| <<<Back 1 day (to 2017/12/21) | 20171222 |
_baskerville_ | If would be great if you could find the time to have a look at 698770. | 10:14.59 |
| This is a show stopper as far as ePUB rendering goes. | 10:15.28 |
kens | Its Chritmas, staffing levels are low | 10:15.41 |
| It also isn't (as far as I can see) a problem normally when rendering ePub, though I'm sure its a problem for you | 10:16.39 |
| Note I am not a MuPDF developer... | 10:17.01 |
_baskerville_ | It seems like a general problem and happens even when the ePUB's CSS is disabled. | 10:18.04 |
kens | I can't comment, I'm not involved with the development | 10:18.18 |
sebras | kens: I need to go out shopping for presents for a bit, but when I'm back I plan to look at 698830. | 10:25.58 |
kens | THe new security bug ? | 10:26.08 |
sebras | kens: that would be the one... | 10:28.27 |
kens | Right, thanks sebras | 10:28.34 |
sebras | kens: I don't think others are more pressing. | 10:31.07 |
kens | No probably not | 10:31.15 |
Piedro | Is sources for MuPDF on Google Play opened and available somewhere? | 13:45.53 |
sakas | Hi. Recently, I switched from the viewer using X11 to the one using OpenGL and noticed that the maximum zoom percentage is quite limited compared to the old viewer using X11. Looking inside the code, I found that MAXRES is set to 1152 in the code for X11 where as it is set to 288 in the code for OpenGL. Is there a reason for this? | 13:45.55 |
Piedro | sakas: To force you into buying MuPDF Pro version) | 13:46.53 |
sakas | Hehe that's not nice | 13:50.38 |
| BTW , isn't this (http://git.ghostscript.com/?p=mupdf.git;a=tree;f=platform/java) the source for the android app? (I'm not a contributor, so it's just a guess) | 13:53.33 |
kens | Piedro, as far as I'm aware *all* MuPDF source ia available. The current viewer on the Google Play store is, I believe behind the current version though. A new version should be along in the New Year | 14:29.40 |
| You can get the sources fromhttp://www.mupdf.com: | 14:30.24 |
| https://mupdf.com/downloads/ | 14:30.24 |
| Notice that the source is at 1.12, while the viewers have not yet been updated and are at 1.11 | 14:30.53 |
| sakas, I doubt there's anyone who can answer your question until next year, its holiday season | 14:31.24 |
Piedro | kens: Don't you mirror the sources at GitHub https://github.com/ArtifexSoftware/mupdf ? | 14:34.35 |
kens | There is a mirror there yes | 14:34.44 |
| The canonical sources are in our own Git repository | 14:34.54 |
| As sakas pointed out | 14:35.05 |
| Please note, I'm not one of the MuPDF develoeprs, so my knowledge is strictly limited | 14:35.37 |
| But since they are all offline or on vacation, I'm the best you can get | 14:35.47 |
Piedro | kens: Do you know at least, will the color inversion be ported to android viewer with New Year's version? | 14:37.34 |
kens | Sorry I have no clue | 14:37.43 |
Piedro | Is there any docs on build process for android platform? | 14:54.21 |
Robin_Watts | Piedro: I don't think we have plans to port the color inversion stuff. | 14:54.24 |
| Piedro: Yep. All the git repos should have build instructions on. | 14:54.50 |
| Failing that mupdf.com will. | 14:54.55 |
Piedro | Robin_Watts: As I understand, color inversion is already there (in library), only the button to switch it in android app is missing. | 14:56.14 |
Robin_Watts | Piedro: Yes. | 14:56.41 |
| And we have no immediate plans to add such a button. | 14:56.56 |
| But it's open source, so go for it. | 14:57.05 |
Piedro | That's what I'm trying right now, but struggling with getting a build running locally)) | 14:57.38 |
sakas | kens: Okay I'll wait. I'm not in a hurry. | 15:02.31 |
Piedro | Robin_Watts: Do you have any roadmap available freely on future plans for MuPDF? | 15:02.39 |
Robin_Watts | Piedro: Nope, sorry. | 15:02.58 |
kens | sakas Robin *might* be able to answer | 15:03.03 |
Robin_Watts | sakas: The code you point at there *was* the code for the android app. | 15:03.43 |
| But it's been pulled out now to a separate repo, I think. | 15:04.01 |
Piedro | Robin_Watts: Then the last thing I want to say is thanks for such an excellent app. | 15:04.26 |
Robin_Watts | That is now the code for the JNI bindings. | 15:04.34 |
Piedro | Robin_Watts: _nui? | 15:05.00 |
Robin_Watts | This is the "old" android viewer (as found on google play): http://git.ghostscript.com/?p=mupdf-android-viewer-old.git;a=summary | 15:05.10 |
kens | New User Interface | 15:05.14 |
Robin_Watts | Piedro: NUI refers to an internal project name we use. | 15:05.43 |
| to do with the development of SmartOffice. | 15:05.51 |
Piedro | I'm trying to build mupdf-android-viewer-nui. | 15:06.05 |
Robin_Watts | We are rejigging stuff so that SmartOffice can use MuPDF for PDF rendering. | 15:06.18 |
| Piedro: Oh, God, Why? | 15:06.23 |
Piedro | It sounded like newest) | 15:06.38 |
Robin_Watts | the -nui one is a work in progress. Don't mess with it yet. | 15:06.44 |
| The cleanest simple, easiest to work with one, is either mupdf-android-viewer.git or mupdf-android-viewer-mini.git | 15:07.26 |
Piedro | Robin_Watts: Which is the difference between mupdf-android-viewer-old (is it mupdf-android-viewer.git ?) and mupdf-android-viewer-mini? | 15:08.13 |
| *What | 15:08.20 |
Robin_Watts | It's to do with the way they are built internally. | 15:08.37 |
| -old predates the proper JNI bindings. | 15:08.51 |
| In order to call from java to C, I made a hacky MuPDFCore thing that exposed just enough of the functionality for what we needed. | 15:09.18 |
Piedro | mupdf-android-viewer.git is it -old or what? | 15:09.34 |
Robin_Watts | But it means that changing stuff in the viewer often needs corresponding changes in the JNI levels - and that is scary for most people. | 15:09.53 |
| So mupdf-android-viewer-mini.git was rewritten to be a simple viewer that used the proper JNI functions. | 15:10.33 |
| correspondingly, it's a lot easier for people to make changes in. | 15:10.44 |
Piedro | Oh, nice, so -mini is the way to go. | 15:11.30 |
| Thanks! | 15:11.34 |
Robin_Watts | mupdf-android-viewer.git is, *I think*, the original viewer bashed about to use the proper JNI code. | 15:11.48 |
| It's not *quite* as powerful as the original one (no form filling, annotations etc), but it's basically the same interface. | 15:12.13 |
Piedro | Is mupdf-android-viewer.git mirrored at the GitHub? | 15:12.20 |
Robin_Watts | If -mini does what you want, then that's the one to use. | 15:12.28 |
| Piedro: Dunno. I don't use github. | 15:12.35 |
sakas | Robin_Watts: Thanks for the correct information | 15:17.26 |
| Robin_Watts: Do you know anything about my original question (which is about the maximum zoom percentage)? | 15:18.50 |
Robin_Watts | sakas: I don't know what the maximum zoom percentage is set to anywhere offhand. | 15:19.23 |
| The core MuPDF lib can cope with almost any percentage you like. | 15:19.43 |
| The limitations are just in what each app has chosen to expose, and should be easy to change. | 15:20.11 |
sakas | Robin_Watts: That's a good news. I'll see what happens by changing the config of the app | 15:25.29 |
| It seems like editing a single line has solved my problem. | 15:53.00 |
| As I expected, changing the value of MAXRES to 1152 in platform/gl/gl-main.c worked | 15:54.44 |
| And I don't see any issue caused by that change | 15:55.53 |
| Robin_Watts: I appreciate your help! | 15:56.26 |
| IMO, editing the zoom_list seems to be a better fix. But, editing MAXRES seems to be the way if one wants to make the gl version consistent with the x11 version | 16:05.13 |
| The last thing I wanna say is thank you for your help and have a nice holiday! | 16:08.15 |
John | Jo | 22:09.55 |
Guest78582 | Faith | 22:10.52 |
janzo | i got a question, using mutool conver filename-%d.png mypdf.pdf 5, the filename is filename-1.png why isnt it -5? | 23:02.39 |
| the image created is page 5 | 23:03.01 |
| draw on the hand outputs proper name | 23:06.30 |
| Forward 1 day (to 2017/12/23)>>> | |