emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Ruijie Yu <ruijie@netyu.xyz>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Q] How to italicize without introducing a space?
Date: Wed, 29 Mar 2023 10:15:36 +0200	[thread overview]
Message-ID: <87r0t80y8n.fsf@mbork.pl> (raw)
In-Reply-To: <sdvr0t8fdy2.fsf@fw.net.yu>


On 2023-03-29, at 05:12, Ruijie Yu via General discussions about Org-mode. <emacs-orgmode@gnu.org> wrote:

> Hello,
>
> I am working on a piece of CJK text, which requires italicization.
>
> --8<---------------cut here---------------start------------->8---
> 任何一个章节可以通过增加例如 =TODO= 或者 =HOLD= 等关键词来被设置成 /待办/ 。
> --8<---------------cut here---------------end--------------->8---
>
> Note the spaces before and after the pair of `?/'.  Without these
> spaces, the HTML export does not show "待办" as italicized, but instead
> treat them as inline literal `?/' characters, which is expected in
> current Org implementation.
>
> Also note that -- unlike English -- Chinese sentences rarely use spaces
> (if at all), so showing the space simply because the Org grammar needs
> it seems unnatural.
>
> However, I don't immediately see how to resolve the issue natively in
> Org.  If we allow `?/' to italicize regardless of spaces, then things
> like Unix paths would no longer work.
>
> So, I came up with using LaTeX like this:
>
> --8<---------------cut here---------------start------------->8---
> 任何一个章节可以通过增加例如 =TODO= 或者 =HOLD= 等关键词来被设置成\(\textit{待办}\)。
> --8<---------------cut here---------------end--------------->8---
>
> This has two drawbacks:
> 1. (network-related?) Delay.  Apparently HTML uses MathJax to render
> LaTeX, and my browser experiences a 1-second delay due to it needing to
> download JS code from MathJax and doing some processing.
> 2. Transferability.  This only resolves the issue of /italicization/.
> What if I need to underscore or bold a piece of text (likely), or to add
> an inline code block with CJK characters (unlikely)?  I would have to
> search for how to do each in LaTeX and write the workaround accordingly,
> instead of simply using the Org markup syntax for each of them.
>
> Are there any other solutions than what I have currently?

My go-to solution (and not only mine, I guess) is to use a zero-width
space.  I even have a command to do this:

(defun insert-zero-width-space ()
  "Insert Unicode character \"zero-width space\"."
  (interactive)
  (insert 8203))

Hth,

-- 
Marcin Borkowski
http://mbork.pl


      parent reply	other threads:[~2023-03-29  8:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29  3:12 [Q] How to italicize without introducing a space? Ruijie Yu via General discussions about Org-mode.
2023-03-29  6:06 ` Dr. Arne Babenhauserheide
2023-03-29  6:18   ` Ruijie Yu via General discussions about Org-mode.
2023-03-29  7:05     ` Dr. Arne Babenhauserheide
2023-03-29  8:15 ` Marcin Borkowski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r0t80y8n.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=emacs-orgmode@gnu.org \
    --cc=ruijie@netyu.xyz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).