From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Maxim Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: ODT export of Chinese text inserts spaces for line breaks
Date: Tue, 29 Jun 2021 11:19:23 -0700 [thread overview]
Message-ID: <87sg10ttxw.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <sbfjkd$7k4$1@ciao.gmane.io> (Maxim Nikulin's message of "Wed, 30 Jun 2021 00:01:00 +0700")
Maxim Nikulin <manikulin@gmail.com> writes:
> On 29/06/2021 10:47, James Harkins wrote:
>> So, it would make sense to add a rule to the exporter: if one of the
>> characters before or after a source-text line break is a Chinese,
>> Japanese or Korean character, do not add a space.
>
> On 29/06/2021 11:43, tumashu wrote:
>> You can try the below config :-)
>> (let ((regexp "[[:multibyte:]]")
>> (string text))
>> (setq string
>> (replace-regexp-in-string
>> (format "\\(%s\\) *\n *\\(%s\\)" regexp regexp)
>> "\\1\\2" string))
>
> Notice that [[:multibyte:]] means almost any non-ASCII script, e.g.
> Cyrillic:
>
> (let ((sample "abc абв def"))
> (and (string-match "[[:multibyte:]]\+" sample)
> (match-string 0 sample)))
> "абв"
>
> It seems, `org-fill-paragraph' M-q is smart enough to avoid a space
> before or after a CJK character, so it is possible to determine
> correct way to splice lines, despite e.g. "Script" Unicode property is
> not exposed to elisp:
> https://www.gnu.org/software/emacs/manual/html_node/elisp/Character-Properties.html
> (Anyway maintaining explicit list of scripts is not a straightforward
> approach.)
There are a few ways to approach this:
(aref char-script-table ?中) -> 'han
(string-match-p "\\cc" "中") -> 0
(aref (char-category-set ?中) ?|) -> t
next prev parent reply other threads:[~2021-06-29 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 3:47 Bug: ODT export of Chinese text inserts spaces for line breaks James Harkins
2021-06-29 4:43 ` tumashu
2021-06-29 17:01 ` Bug: " Maxim Nikulin
2021-06-29 18:19 ` Eric Abrahamsen [this message]
2021-06-30 12:22 ` Maxim Nikulin
2022-10-08 13:14 ` Ihor Radchenko
2022-10-21 5:38 ` Ihor Radchenko
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=87sg10ttxw.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
/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).