Update of bug #66432 (group groff):
Summary: [troff] want `device` request to support composite
special character escape sequences => [troff] want `device` request to support
composite special character escape sequences like `\[e aa]`
_______________________________________________________
Follow-up Comment #2:
Clarifying summary because this is yet another area where *roff developers
found a term they liked and used it for several different purposes in contexts
not distant from each other.
_groff_char_(7) defines a _composite special character escape sequence_.
\[base‐char composite‐1 composite‐2 ... composite‐n]
is a composite glyph. Glyphs like a lowercase “e” with an
acute accent, as in the word “café”, can be expressed as \[e
aa].
Internally, there is an object type known as a `composite_node`. This term is
applied to characters that have string ("macro") definitions (with no internal
newlines allowed, thus strings). They (can) contain multiple children (the
tokens in the string), thus "composite".
Not the same thing, but composite nodes can contain special character glyph
nodes produced by...composite special character escape sequences.
I swear, some hackers name things like they're Mike Vronsky, and they just
manically glare at you, Nick Chevotarevich, as they hand you a revolver with
five chambers loaded.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66432>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
