From: Eli Zaretskii <eliz@gnu.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 47857@debbugs.gnu.org
Subject: bug#47857: fill-paragraph vs. FULLWIDTH DIGITs: bug exposed
Date: Tue, 20 Apr 2021 14:29:37 +0300 [thread overview]
Message-ID: <83wnsxqjmm.fsf@gnu.org> (raw)
In-Reply-To: <87fszln9di.5.fsf@jidanni.org> (message from 積丹尼 Dan Jacobson on Tue, 20 Apr 2021 07:27:05 +0800)
> From: 積丹尼 Dan Jacobson <jidanni@jidanni.org>
> Cc: 47857@debbugs.gnu.org
> Date: Tue, 20 Apr 2021 07:27:05 +0800
>
> EZ> I don't see any bug here. This is the documented behavior: filling
> EZ> deletes any excess whitespace, so 2 or more consecutive SPC characters
> EZ> are squeezed to a single SPC.
>
> Ah, but one needs
>
> Today's lucky number(s)!: <-added space here
> 9 <-added space here
> 10 <-added space here
> 11
>
> to keep the whitespace in with fill-paragraph, whereas no spaces are
> required for
>
> Today's lucky number(s)!:
> 9
> 10
> 11
>
> To safely become:
>
> Today's lucky number(s)!: 9 10 11
This is a feature: full-width Latin characters, such as 0, 1, and 9,
are exempted from converting newlines into spaces during filling.
They follow the rules of other CJK characters, which are processed the
same. I think it's because of line-breaking rules: we can break the
line between any 2 CJK characters, including those above, and thus
adding spaces where there were newlines is superfluous, as it would
artificially create separate words where only one has been before.
prev parent reply other threads:[~2021-04-20 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 1:06 bug#47857: fill-paragraph vs. FULLWIDTH DIGITs: bug exposed 積丹尼 Dan Jacobson
2021-04-18 6:52 ` Eli Zaretskii
2021-04-18 16:27 ` Stefan Kangas
2021-04-19 23:27 ` 積丹尼 Dan Jacobson
2021-04-20 11:29 ` Eli Zaretskii [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wnsxqjmm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47857@debbugs.gnu.org \
--cc=jidanni@jidanni.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.