mirror of
https://github.com/qpdf/qpdf.git
synced 2024-09-21 09:39:09 +00:00
3246923cf2
Also refine the herustic for deciding whether to use hexadecimal notation for a string.
61 lines
2.9 KiB
Plaintext
61 lines
2.9 KiB
Plaintext
-- stream 0 --
|
|
A %here is a comment
|
|
B % here is another with CR
|
|
A B
|
|
|
|
one
|
|
two
|
|
three lines
|
|
(string with \nCRLF and\nCR and\nLF)
|
|
and another
|
|
indentation
|
|
<014225444546><01>
|
|
<8a8b>
|
|
(ab)
|
|
<8c><dd> ) >
|
|
<610062> (MOO)WARNING: good14.pdf (offset 628): content normalization encountered bad tokens
|
|
WARNING: good14.pdf (offset 628): Resulting stream data may be corrupted but is may still useful for manual inspection. For more information on this warning, search for content normalization in the manual.
|
|
-- stream 1 --
|
|
This stream does end with a newline.
|
|
// tests:
|
|
// bad tokens preserved
|
|
// comments
|
|
// indentation
|
|
// CR, CR/LF, LF inside string literal -- changed to \n
|
|
// whitespace in hexstring (removed)
|
|
// strings normalized
|
|
// newlines normalized
|
|
// names normalized
|
|
// trailing space (preserved)
|
|
// final newline added
|
|
|
|
/bad#name
|
|
|
|
/good name
|
|
/bad#00name
|
|
WARNING: good14.pdf (offset 874): content normalization encountered bad tokens
|
|
WARNING: good14.pdf (offset 874): Resulting stream data may be corrupted but is may still useful for manual inspection. For more information on this warning, search for content normalization in the manual.
|
|
-- stream 2 --
|
|
(This stream ends with a \001 bad token
|
|
WARNING: good14.pdf (offset 1315): content normalization encountered bad tokens
|
|
WARNING: good14.pdf (offset 1315): normalized content ended with a bad token; you may be able to resolve this by coalescing content streams in combination with normalizing content. From the command line, specify --coalesce-contents
|
|
WARNING: good14.pdf (offset 1315): Resulting stream data may be corrupted but is may still useful for manual inspection. For more information on this warning, search for content normalization in the manual.
|
|
-- stream 3 --
|
|
<AB XWARNING: good14.pdf (offset 1405): content normalization encountered bad tokens
|
|
WARNING: good14.pdf (offset 1405): normalized content ended with a bad token; you may be able to resolve this by coalescing content streams in combination with normalizing content. From the command line, specify --coalesce-contents
|
|
WARNING: good14.pdf (offset 1405): Resulting stream data may be corrupted but is may still useful for manual inspection. For more information on this warning, search for content normalization in the manual.
|
|
-- stream 4 --
|
|
(ends with a name)
|
|
/ThisMustBeLast-- stream 5 --
|
|
% This stream has an inline image marker that is not terminated
|
|
(Potato)
|
|
|
|
BI
|
|
ID
|
|
<506f7
|
|
461746f>
|
|
WARNING: good14.pdf (offset 1548): content normalization encountered bad tokens
|
|
WARNING: good14.pdf (offset 1548): normalized content ended with a bad token; you may be able to resolve this by coalescing content streams in combination with normalizing content. From the command line, specify --coalesce-contents
|
|
WARNING: good14.pdf (offset 1548): Resulting stream data may be corrupted but is may still useful for manual inspection. For more information on this warning, search for content normalization in the manual.
|
|
test 3 done
|