Log of #mupdf at irc.freenode.net.
| <<<Back 1 day (to 2019/08/11) | Fwd 1 day (to 2019/08/13)>>> | 20190812 | |
| Robin_Watts | sebras: http://git.ghostscript.com/?p=user/robin/mupdf.git;a=commitdiff;h=c8d02c80556b93e1d047420b703f025357781fa0 | 09:49.55 | |
| Just clustering that now. | 09:50.00 | ||
| sebras | Robin_Watts: should we also test against PDF_MAX_OBJECT_NUMBER ? | 09:52.04 | |
| Robin_Watts: and quite possibly a maximum generation number? | 09:52.14 | ||
| perhaps that's for a separate commit, I don't know. I haven't thought this through. it's just my immediate reaction. | 09:52.37 | ||
| Robin_Watts | sebras: I don't know that there is a maximum valid object number, is there? | 09:54.48 | |
| ooh, that constant exists. | 09:55.22 | ||
| We probably should. | 09:55.25 | ||
| Let me update the commit | 09:55.46 | ||
| sebras | yes it does. I've used it. :) | 09:56.29 | |
| Robin_Watts | http://git.ghostscript.com/?p=user/robin/mupdf.git;a=commitdiff;h=8d9bc1961b308507da047497843b820528e5c5bb | 09:58.13 | |
| sebras | the maximum generation number is 65535 according to page 95 in pdfref17.pdf | 10:02.06 | |
| that probably doesn't matter for the bug, but is it worth taking into account? | 10:02.26 | ||
| Robin_Watts | Can't hurt. | 10:12.36 | |
| http://git.ghostscript.com/?p=user/robin/mupdf.git;a=commitdiff;h=0ced8361cca6d5536f9d770a432459189c08f884 | 10:21.35 | ||
| bah. let me fix the message. | 10:21.48 | ||
| http://git.ghostscript.com/?p=user/robin/mupdf.git;a=commitdiff;h=01226d0c092b4f1ac6c06cb574e628764e53577b | 10:23.23 | ||
| sebras | Robin_Wattsv LGTM | 10:37.37 | |
| Robin_Watts | sebras: Ta. | 10:52.45 | |
| <<<Back 1 day (to 2019/08/11) | Forward 1 day (to 2019/08/13)>>> | ||