Add a New Comment Rich Markup
Updates to the "two real-world cases" in the original submission:
The Texinfo manual clearly states: "Only the current font is checked for ligatures and kerns; neither special fonts nor entities defined with the 'char' request (and its siblings) are taken into account." This limitation seems the wrong default. If kerning were done by default for .char-defined characters, users who want to disable kerning before or after such a character could do so with \&. Instead, currently such kerning is inactive by default, and there is really no way to tell groff to turn it on. Two real-world cases where this matters:
On the email list, I proposed changing this behavior (http://lists.gnu.org/archive/html/groff/2021-01/msg00031.html), and while responses were extremely limited, no one opposed the idea.
(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)
Attach Files: Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Only logged-in users can vote.
Please enter the title of George Orwell's famous dystopian book (it's a date):
Copyright © 2023 Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team. Source Code
Powered by Savane 3.12