From: Ihor Radchenko <yantar92@posteo.net>
To: Haojun Bao <baohaojun@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [BUG] Can't export bold html correctly after change org-emphasis-regexp-components [9.6.6 (release_9.6.6 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)]
Date: Sat, 04 Nov 2023 12:42:36 +0000 [thread overview]
Message-ID: <87r0l5bsg3.fsf@localhost> (raw)
In-Reply-To: <CAABrf9bAb0KU2db6gP1fvqZxdoi7agJvmFcpCSH08TXZpNrviQ@mail.gmail.com>
Haojun Bao <baohaojun@gmail.com> writes:
> 1. update org-emphasis-regexp-components, as I'm a Chinese, I added
> some of the chinese Punctuation Marks, like the following:
> ...
> 2. do M-x org-reload
> 3. Write a file with the following content, note that both hello is
> displayed as bold:
>
> *hello*:world
>
> *hello* world
>
> 4. C-c C-e to export it as html, only the second hello is in bold, the
> first hello is surrounded by the org bold marker '*'.
Org markup syntax is not customizeable. You may consider using escape
character instead. See https://orgmode.org/manual/Escape-Character.html
`org-emphasis-regexp-components' only affects the fontification, not
actual underlying markup.
We are well aware about this problem for Chinese users. The proper
solution will involve alternative markup like @bold{...} or (maybe)
**creole inline markup**. But changing Org syntax is not something we
can take lightly.
See https://list.orgmode.org/orgmode/87a6b8pbhg.fsf@posteo.net/
Not a bug.
Canceled.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-11-04 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 4:12 [BUG] Can't export bold html correctly after change org-emphasis-regexp-components [9.6.6 (release_9.6.6 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)] Haojun Bao
2023-11-04 12:42 ` Ihor Radchenko [this message]
2023-11-04 14:16 ` Haojun Bao
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=87r0l5bsg3.fsf@localhost \
--to=yantar92@posteo.net \
--cc=baohaojun@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).