From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9286@debbugs.gnu.org, cyd@stupidchicken.com, handa@m17n.org,
jidanni@jidanni.org, 34463@debbugs.gnu.org
Subject: bug#34463: bug#9286: fill-paragraph destroys URLs
Date: Fri, 11 Oct 2019 08:58:52 +0200 [thread overview]
Message-ID: <87eezjpy37.fsf@gnus.org> (raw)
In-Reply-To: <8336g1t59w.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 10 Oct 2019 10:43:07 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Since Kenichi didn't respond, I think we should study what the Unicode
> Line-breaking Algorithm has to say about that. Can you look there for
> relevant guidance? We don't yet implement the complete algorithm, but
> some of what they say could nevertheless be used to resolve this
> issue.
That would be this:
https://unicode.org/reports/tr14/
I have just skimmed it, but I can't see that it says anything helpful
about filling/folding lines.
If I read it correctly, then it's perfectly allowed to line-break
asdf國
into
asdf
國
But it doesn't say what software should do when filling
asdf
國
Presumably filling that into
asdf國
would be correct in many circumstances, but as Dan said, if it's really
http://google.com
國
then filling that into
http://google.com國
is most likely wrong. So if we want to be cautious, then applying
Chong's patch seems to be the right thing: Adding the space will lead
to things working more of the time, while the downside is that somebody
might prefer
asdf國
visually. I think.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-11 6:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 21:25 bug#9286: fill-paragraph destroys URLs jidanni
2011-08-20 19:58 ` Chong Yidong
2019-10-09 22:30 ` Lars Ingebrigtsen
2019-10-10 7:43 ` Eli Zaretskii
2019-10-11 6:58 ` Lars Ingebrigtsen [this message]
2019-11-23 14:00 ` bug#34463: " Lars Ingebrigtsen
2011-08-20 20:04 ` jidanni
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eezjpy37.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=34463@debbugs.gnu.org \
--cc=9286@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=handa@m17n.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).