[bug #64484] [troff] .device should encode special characters in `\[uXXXX]` form

[Deri James]

Follow-up Comment #26, bug #64484 (group groff):

Your \h'1i' example in \X is definitely a horizontal movement, and elicits an
appropriate error. The input characters " ", "\ ", "\~" and "\0" all result in
a horizontal movement, but the user does not know that, to them they all mean
they want a visible gap between adjacent words, the choice of which they use
gives some control over the size of the word gap, but they all signify the
user intends a space sized gap between words.

The first three emit a space (good, that's what the user wanted) but \0 emits
the horizontal movement warning. For consistency they all should be treated
the same, either error or output a space.

\| and \^ should be silently ignored, as they are by nroff, so groff already
has the rule these are ignored in text based output, which is essentially the
contents of \X.

I like your "expert mode for experts" idea, particularly when you move to full
utf8 for groff, since you would pass the original utf8 string to the driver.
The only suggestion I have is that the grout language be extended, rather than
both modes producing "x X" could they be differentiated in some way.




    _______________________________________________________

Reply to this item at:

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

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

signature.asc
Description: PGP signature