[bug #51568] gropdf: Bug when string '\e014' is in the input

[Bjarni Ingi Gislason]

Follow-up Comment #3, bug #51568 (project groff):


Subject: The fix of bug #51568 is too specific

  This was discovered in "groff.7".

  Testfile:

.pl 10
Octal number 1: \e01, \e001
.br
Octal number 7: \e07, \e007
.br
Octal number 8: \e10, \e010
.br
Octal number 9: \e11, \e011
.br
Octal number 33: \e41, \e041
.br
Print an escape \e isolated.
.br
Print an escape at the end of a line\e
Next line

  Command:

groff -Tpdf

  Output:

  Lines with "Octal number" show '\' and the glyph in the first column and
the octal number in the second (\0xx)

  Lines with input "\exx" have '\\\' instead of just '\\' in the PDF file.

  Conclusion:

  Where '\' is in the intermediate output, there must be a '\\' in the PDF
file.  That is independet of what follows.

  This should at least be valid for the intermediate output whose lines begin
with the command 't' or 'u'.

N.B.
  I don't think, that the intermediate output ever contains an octal number
(\0...) that has to be interpreted by the postprocessors to be somethings
else than a text string, namely literatim "\0...".



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51568>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/