unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sebastian Urban <mrsebastianurban@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48654@debbugs.gnu.org
Subject: bug#48654: Overfull hbox, Unicode code points style (display.texi)
Date: Wed, 26 May 2021 09:37:37 +0200	[thread overview]
Message-ID: <5db3ff2d-1c26-35cb-084a-0ef3d48928a6@gmail.com> (raw)
In-Reply-To: <83lf82bufx.fsf@gnu.org>

 >> 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.

Hmmm... which one is incorrect?

 > Also, why remove @code{..} from the "U+NNNN" notation -- what does
 > that solve?

Because, ~2 years ago you decided to follow Unicode docs notation, and
I'm just fixing the leftovers. See your commit:
http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=f68b33f50299339a36da29cd1913d19fd5f288e0

 >> 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.

I don't know if it's a good idea to keep this just in case someone
changes the text in the future, or makes PDF using A5 page format.
Currently (official PDF), it's not close to a line break.

But if it stays, I suggest moving it to DOCSTYLE.TEXI, where other
problematic words are gathered below this line:
   @c It turns out TeX sometimes fails to hyphenate, so we help it here
   @hyphenation{...}






  reply	other threads:[~2021-05-26  7:37 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
2021-05-26  7:37   ` Sebastian Urban [this message]
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=5db3ff2d-1c26-35cb-084a-0ef3d48928a6@gmail.com \
    --to=mrsebastianurban@gmail.com \
    --cc=48654@debbugs.gnu.org \
    --cc=eliz@gnu.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).