[bug #64360] [gropdf] does not correctly handle white space after 'w' command

[Deri James]

Follow-up Comment #10, bug #64360 (project groff):

Yes, I have seen multiple "w", but never one followed by a space.

I thought commands and arguments with a known fixed length (such as the w
command) aren't separated by syntactical space. Well, that was true until
now.

Previously, before you added /n, a w is always followed by another command,
which is what my code expects. I can't see a reason for the change, it is
actually helpful, when looking at troff output, to quickly distinguish word
spaces whnnn and kerning hnnn.

I have not seen your discussion on changing this on the list, I did see your
suggestion about adding a word mark to \~ but not changing the syntax of the
file produced by troff.


    _______________________________________________________

Reply to this item at:

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

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