From: Maxim Nikulin <firstname.lastname@example.org>
Subject: Re: Bug: ODT export of Chinese text inserts spaces for line breaks
Date: Wed, 30 Jun 2021 19:22:21 +0700 [thread overview]
Message-ID: <email@example.com> (raw)
On 29/06/2021 10:47, James Harkins wrote:
> * Test
> Exporting to ODT produces the following (body text, omitting titles,
> headers and such).
> 1本人不想亲自拿到学历学位证书、急于离校者,可书面委托他人代领学历学位证 书,29日起即可离校;2本人想亲自领取学历学位证书者,按学校规定的程序及有关 要求办理离校手续,领取相关证书后离校;
Confirmed: newlines are copied to ODT document as is and they appear as
spaces in libreoffice. I did not tried HTML since I am unsure if
browsers should glue paragraphs with newlines into continuous string
without spaces. Maybe it is necessary to add some attributes for proper
representation (e.g. "lang"), however "#+LANGUAGE: cn" does not help
even though libreoffice considers paragraph as Chinese.
On 30/06/2021 01:19, Eric Abrahamsen wrote:
> There are a few ways to approach this:
> (aref char-script-table ?中) -> 'han
> (string-match-p "\\cc" "中") -> 0
> (aref (char-category-set ?中) ?|) -> t
Thank you. I have not noticed all features hidden behind \c. I believe,
(rx (category can-break))
is more readable and I am a bit surprised that there is no descriptive
aliases char-categories such as ?|. Just to add another example:
(category-set-mnemonics (char-category-set ?ф)) -> ".LYchjy"
and `describe-categories' to decipher it.
As to splicing lines, I found `fill-delete-newlines' that uses
`fill-nospace-between-words-table' besides ?| category to determine
whether space should be suppressed while splicing lines. In addition
there are some variables to tune behavior.
next prev parent reply other threads:[~2021-06-30 12:23 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
2021-06-30 12:22 ` Maxim Nikulin [this message]
2022-10-08 13:14 ` Ihor Radchenko
2022-10-21 5:38 ` Ihor Radchenko
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).