From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: How to force markup without spaces
Date: Tue, 26 Jul 2022 13:30:36 +0700 [thread overview]
Message-ID: <tbo1md$gar$1@ciao.gmane.io> (raw)
In-Reply-To: <80f0990042a564556cc6b047a94f7e9dddf5a280.camel@outlook.com>
On 26/07/2022 11:26, K K wrote:
> On 2022-07-26 Tue. 09:23 +0700，Max Nikulin wrote：
>
>> > However the suggestion was namely to use U+200B ZERO WIDTH SPACE and
>> > it
>> > is actually implemented since `org-emphasis-regexp-components'
>> > currently
>> > contains [:space:].
>> > ...
>> > K, could you, please, clarify what is your particular use case?
>
> My bad, I misunderstood the "feature" mentioned in the old post.
>
> My use case is to emphasize chinese characters without spaces being
> inserted, even those zero-width spaces. For example "中文*测*试" should
> be enough to emphasize "测".
>
> I am using zero-width spaces right now, and it works fine in org-mode
> buffers, but if exported to latex-pdf files, the U+200B ZERO WIDTH SPACE
> character will not be zero-width for certain fonts. So I hope not to use
> that character.
I have not tested it, but I expect you can use
- export filter that removes zero-width spaces at the last export stage.
I assume that your documents do not contain them besides markup workaround
- #+latex_header: \DeclareUnicodeCharacter{200B}{}
- custom link
#+begin_src elisp :results none :exports both
(org-link-set-parameters
"sep"
:export (lambda (path desc backend)
(if (org-export-derived-backend-p backend 'org)
(org-link-make-string (concat "sep:" path) desc)
(or desc ""))))
#+end_src
"中文[[sep:][*测*]]试"
https://list.orgmode.org/ssp8e7$ah2$1@ciao.gmane.io/
Max Nikulin Re: [RFC] Creole-style / Support for
**emphasis**__within__**a word** Tue, 25 Jan 2022 23:27:50 +0700
In other thread we are discussing advantages and problems of switching
from PdfLaTeX to LuaLaTeX for non-latin scripts. The latter is a Unicode
engine. I am curious what is your opinion from standpoint of Chinese
language, namely amount of required customization in both cases. I
think, it is better to either start a dedicated thread, or find the part
of discussion related to fonts and babel (LaTeX package) setup.
next prev parent reply other threads:[~2022-07-26 6:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 5:32 How to force markup without spaces cinsky
2012-11-19 7:11 ` Vladimir Lomov
2012-11-19 10:06 ` Seong-Kook Shin
2012-11-19 14:40 ` Suvayu Ali
2012-12-13 21:26 ` Bastien
2022-07-25 17:50 ` K
2022-07-25 18:27 ` K
2022-07-25 19:02 ` K
2022-07-26 1:26 ` Ihor Radchenko
2022-07-26 2:23 ` Max Nikulin
2022-07-26 4:26 ` K K
2022-07-26 6:30 ` Max Nikulin [this message]
2022-07-26 12:59 ` [PATCH] org-export: Remove zero-width space escapes during export Ihor Radchenko
2022-07-26 14:25 ` Timothy
2022-07-26 15:27 ` András Simonyi
2022-07-26 16:38 ` Max Nikulin
2022-07-27 3:30 ` Max Nikulin
2022-07-28 13:17 ` [PATCH] Add new entity \-- serving as markup separator/escape symbol Ihor Radchenko
2022-07-28 15:34 ` Max Nikulin
2022-07-29 1:43 ` Ihor Radchenko
2022-07-29 2:50 ` Max Nikulin
2022-07-29 9:06 ` [PATCH v2] " Ihor Radchenko
2022-07-30 0:22 ` Samuel Wales
2022-07-30 4:12 ` Samuel Wales
2022-07-30 6:49 ` Ihor Radchenko
2022-07-30 15:44 ` Max Nikulin
2022-07-28 22:20 ` [PATCH] " Tim Cross
2022-07-29 0:32 ` Juan Manuel Macías
2022-07-29 5:49 ` tomas
-- strict thread matches above, loose matches on Subject: below --
2022-07-26 10:24 How to force markup without spaces K
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='tbo1md$gar$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).