Update of bug #55155 (project groff):
Status: Confirmed => Need Info
Assigned to: None => barx
_______________________________________________________
Follow-up Comment #7:
I'm thinking we need a stronger distinction, in documentation and possibly in
code, between translations of _characters_ (those things that are manipulated
before conversion into glyph entities for the output device) and _glyphs_
(things that the output device is expected render at a certain size using a
certain font, possibly with other properties like stroke color and slant).
We might even need two more categories. :(
1. input character remapping (`trin`; handles character encoding issues from
the input file stream)
2. character lookup remapping (`tr`); once a character is canonicalized into
the "groff character set", you can switch them around
3. rewriting/redefinition of output character entities (`char` and friends);
this determines what is produced in the "grout" commands `C`, `c`, `t`, `u`,
and the legacy, "optimized" encoding described in CSTR #97.
4. what an output device produces with (virtual) ink on a (virtual) page
If this is sensible and coherent, it means I'm closer to being ready to revise
the "Using Symbols" section of our Texinfo manual.
Throwing to you for feedback.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?55155>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
