Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
monsters [2021/07/23 17:41] christian [Incorrect stream length] |
monsters [2021/07/24 08:12] (current) christian [Incorrect stream length] |
||
---|---|---|---|
Line 51: | Line 51: | ||
===== Incorrect stream length ===== | ===== Incorrect stream length ===== | ||
- | The ''/ | + | The ''/ |
+ | |||
+ | The following cases are possible: | ||
+ | * ''/ | ||
+ | * ''/ | ||
+ | |||
+ | The particular monster where I encountered this, had always one byte too much in the content. Therefore, not the general problem was handled, but just the simple case where the content is exactly 1 larger | ||
=== Example === | === Example === | ||
Line 71: | Line 77: | ||
If there are more bytes extra, a '' | If there are more bytes extra, a '' | ||
+ | |||
+ | == Known problem == | ||
+ | |||
+ | The general problem has not been adressed. One idea is to find the end of the stream content of the current object. With this information it is possible to determine if the ''/ | ||
+ | |||
+ | The end of the stream would be before the '' | ||
+ | |||
+ | Object streams need not be considered, because they cannot contain streams. | ||
+ | |||
+ | This should be easy for the simple case of only one xref table. But handling several xrefs from different updates deemed too complex at the time (that' | ||
=== Reference === | === Reference === | ||
Seen in ''/ | Seen in ''/ |