Update of bug #66653 (group groff):

                 Summary: [PATCH] [troff].asciify odd behaviour / adding pdf
features to ms => [PATCH] [troff] .asciify odd behaviour / adding pdf features
to ms

    _______________________________________________________

Follow-up Comment #25:

[comment #21 comment #21:]
> As far as I know the special character '\A' does not exist as a groff name,
> it is not mentioned in groff_char.

That's correct.  The only special character name with a single-character
_groff_ predefines is `\[-]`, more familiar as `\-`.

_groff_char_(7):

       \C'c' and \[c] are not synonyms for the ordinary character “c”,
       but request the special character named “\c”.  For example,
       “\[a]” is not “a”, but rather a special character with the
       internal glyph name (used in font description files and
       diagnostic messages) \a, which is typically undefined.  The only
       such glyph name groff predefines is the minus sign, which can
       therefore be accessed as \C'-' or \[-].


There are other "single-character" special characters, like `\_`, but they get
remapped to longer identifiers at input processing.

_groff_char_(7):

       A few escape sequences that are not groff special characters also
       produce glyphs; these exist for syntactical or historical
       reasons.  \', \`, \-, and \_ are translated on input to the
       special character escape sequences \[aa], \[ga], \[-], and \[ul],
       respectively.  Others include \\, \. (backslash‐dot), and \e; see
       groff(7).  A small number of special characters represent glyphs
       that are not encoded in Unicode; examples include the baseline
       rule \[ru] and the Bell System logo \[bs].


> I'm dealing with groff's problems with more modern fonts in my forthcoming
> reply to bug #67244, which is taking an age to write as I keep getting
> sidetracked into writing little utility programs discovering the innards of
> ttf and otf fonts.

Ooh, I'm excited to see what this yields.




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?66653>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to