groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Groff] unicode support, part 10: \[shc]


From: Bruno Haible
Subject: [Groff] unicode support, part 10: \[shc]
Date: Tue, 21 Feb 2006 18:51:40 +0100
User-agent: KMail/1.5

Werner Lember wrote:
> Under normal circumstances, `shc' is never a glyph in groff.  From the
> NEWS file:
> 
>   Using the latin-1 input character 0xAD (soft hyphen) for the `shc'
>   request was a bad idea.  Instead, it is now translated to `\%', and
>   the default hyphenation character is again \[hy].  Note that the
>   glyph \[shc] is not useful for typographic purposes; it only exists
>   to have glyph names for all latin-1 characters.
> 
> With other words, if you need a soft hyphen, use `\%', not \[shc].
> The file `latin1.tmac' does the same.

So it should make sense to align glyphuni.cpp to what all devices do.
I propose this patch.


2006-02-19  Bruno Haible  <address@hidden>

        * glyphuni.cpp (glyph_to_unicode_list): Comment out the entry for
        \[shc].

diff -r -c3 groff-20060217.orig/src/libs/libgroff/glyphuni.cpp 
groff-20060217/src/libs/libgroff/glyphuni.cpp
--- groff-20060217.orig/src/libs/libgroff/glyphuni.cpp  2006-02-15 
12:55:49.000000000 +0100
+++ groff-20060217/src/libs/libgroff/glyphuni.cpp       2006-02-19 
18:39:02.000000000 +0100
@@ -170,7 +170,9 @@
   { "Fo", "00AB" },
   { "no", "00AC" },
   { "tno", "00AC" },
-  { "shc", "00AD" },
+// The glyph \[shc] is not useful for typographic purposes.
+// U+00AD is meaningful only in the input file, not in the output.
+//{ "shc", "00AD" },
   { "rg", "00AE" },
   { "a-", "00AF" },
   { "de", "00B0" },





reply via email to

[Prev in Thread] Current Thread [Next in Thread]