diff options
| author | Jay Berkenbilt <ejb@ql.org> | 2019-01-31 21:51:52 +0100 |
|---|---|---|
| committer | Jay Berkenbilt <ejb@ql.org> | 2019-02-01 02:28:44 +0100 |
| commit | eb49e07c0afc1b30b53d3ae2849c824c9407f00d (patch) | |
| tree | e7c73b1115fcd5b7ea3c62376cb10e680724fb1c /ChangeLog | |
| parent | 5211bcb5eaa2b6b3c8aa48580f1b97314c37bb4a (diff) | |
| download | qpdf-eb49e07c0afc1b30b53d3ae2849c824c9407f00d.tar.zst | |
Make inline image token exactly contain the image data
Do not include the trailing EI, and handle cases where EI is not
preceded by a delimiter. Such cases have been seen in the wild.
Diffstat (limited to 'ChangeLog')
| -rw-r--r-- | ChangeLog | 8 |
1 files changed, 6 insertions, 2 deletions
@@ -26,10 +26,14 @@ * Very low-level QPDFTokenizer API now includes an expectInlineImage method that takes an input stream, enabling it - to locate an inline image's EI operator better. This is called + to locate an inline image's EI operator better. When this method + is called, the inline image token returned will not contain the EI + operator and will contain correct image data. This is called automatically everywhere within the qpdf library. Most user code will never have to use the low-level tokenizer API. If you use - Pl_QPDFTokenizer, this will be done automatically for you. + Pl_QPDFTokenizer, this will be done automatically for you. If you + use the low-level API and call expectInlineImage, you should call + the new version. 2019-01-29 Jay Berkenbilt <ejb@ql.org> |