diff options
Diffstat (limited to 'docs/progressive.txt')
| -rw-r--r-- | docs/progressive.txt | 6 |
1 files changed, 1 insertions, 5 deletions
diff --git a/docs/progressive.txt b/docs/progressive.txt index a39e70d9..081f599e 100644 --- a/docs/progressive.txt +++ b/docs/progressive.txt @@ -16,7 +16,6 @@ For optimum performance a file should be both linearized and be available over a byte-range supporting link, but benefits can still be had with either one of these alone. - Progressive download using "linearized" files ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -54,7 +53,6 @@ uses, shared or otherwise, subsequent pages do not get shared resources until after all the unshared page objects have been sent.] - The Hint Stream ~~~~~~~~~~~~~~~ @@ -67,7 +65,6 @@ Consequently very few people actually use it. MuPDF will use it after sanity checking the values, and should cope with illegal/ incorrect values. - So how does MuPDF handle progressive loading? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -148,7 +145,6 @@ progressive loading. the caller can check the value of the 'incomplete' field and know that the rendering it received is not authoritative. - Progressive loading using byte range requests ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -248,7 +244,7 @@ a server. non-linear file can be 20%+ of the file data. Once past this initial point however, pages and data can be pulled from the file almost as fast as with a linearized file.] - + For a non-linearized PDF on a non-byte request capable stream: - MuPDF will immediately seek to the end of the file to attempt |