From: Eli Zaretskii <eliz@gnu.org>
To: Sebastian Urban <mrsebastianurban@gmail.com>
Cc: 48654@debbugs.gnu.org
Subject: bug#48654: Overfull hbox, Unicode code points style (display.texi)
Date: Tue, 25 May 2021 20:21:38 +0300 [thread overview]
Message-ID: <83lf82bufx.fsf@gnu.org> (raw)
In-Reply-To: <1b291257-516b-e751-1a7b-79823964ad16@gmail.com> (message from Sebastian Urban on Tue, 25 May 2021 17:24:44 +0200)
> From: Sebastian Urban <mrsebastianurban@gmail.com>
> Date: Tue, 25 May 2021 17:24:44 +0200
>
> Changes are in the attached DIFF file (DISPLAY.DIFF).
>
> As for the "overfull hbox", in the end I decided to simply add a
> discretionary hyphen (@-) after 2nd hyphen (when I added it after
> every hyphen, the line was broken after 2nd hyphen). Alternatively,
> someone will have to rearrange the sentence.
>
> As for Unicode code points it was decided to use "U+NNNN @sc{char
> name}", so I adjusted all of them.
Please use the exact names of the characters as they appear in the
UnicodeData.txt file.
Also, why remove @code{..} from the "U+NNNN" notation -- what does
that solve?
> Finally, in a different file - FIXIT.TEXI - there is line 356, where
> the word "dictionary" uses a discretionary hyphens - are they used
> somewhere? Because, in the PDF there is no line breaking for this
> sentence and if it's correct, perhaps adding this word to
> DOCSTYLE.TEXI would be a better option.
It depends on surrounding text: if the word gets close to a line
break, we want it to break correctly.
next prev parent reply other threads:[~2021-05-25 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 15:24 bug#48654: Overfull hbox, Unicode code points style (display.texi) Sebastian Urban
2021-05-25 17:21 ` Eli Zaretskii [this message]
2021-05-26 7:37 ` Sebastian Urban
2021-05-26 12:38 ` Eli Zaretskii
2021-05-26 19:00 ` Sebastian Urban
2021-05-29 8:24 ` Eli Zaretskii
2021-05-29 16:50 ` Sebastian Urban
2021-06-06 10:00 ` Eli Zaretskii
2021-06-07 13:17 ` Sebastian Urban
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=83lf82bufx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48654@debbugs.gnu.org \
--cc=mrsebastianurban@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.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).