| | <<<Back 1 day (to 2016/06/05) | 20160606 |
| psmlbhor | hello, I have a PS file which I have generated. The document viewer and okular viewer correctly shows the output but GhostScript interpreter does not. How I make it work with GS? | 06:59.36 |
| kens | What do you mean by 'Ghostscript does not' ? Its very unlikely that the viewers you are using do anything other than send the PostScript to Ghostscript anyway. | 07:00.22 |
| psmlbhor | kens, I run the gs as $ghostscript myfile.ps but it shows very big window which cannot be scrolled | 07:01.25 |
| kens | So you are using the display device, and I presume on Linux ? | 07:01.55 |
| psmlbhor | yes | 07:02.00 |
| kens | Well the other document viewers will be using Ghostscript to create a bitmap (eg PNG) and loading the, rather than using the display device. | 07:02.40 |
| | The first thing you could do is reduce the resolution | 07:02.49 |
| | It sounds to me like the PostScript file requests a high resolution, try using -r96 on the command line | 07:03.11 |
| psmlbhor | ok, I will try it and let you know | 07:04.14 |
| kens | Which version of Ghostscript are you using ? | 07:04.26 |
| psmlbhor | -r96 did not work. Ghostscript version 9.18 | 07:05.59 |
| kens | OK so when you say 'did not work' what do you mean ? error message ? crash ? something else ? | 07:06.25 |
| | And can you share the source file ? It will be a lot easier to help that way | 07:06.47 |
| psmlbhor | no, same thing. A window but smaller size than before which cannot be scrolled | 07:06.51 |
| | yes | 07:06.55 |
| kens | OK if you can put it on dropbox or something I'll take a look | 07:07.09 |
| | The smaller window says that its not a size problem, its simply a blank page. No messages on stdout ? | 07:07.31 |
| psmlbhor | No message on stdout | 07:08.05 |
| kens | OK then I'll have to look at the file | 07:08.19 |
| psmlbhor | i am uploading the file to my google drive. I'll share the link | 07:09.07 |
| kens | OK | 07:09.14 |
| psmlbhor | https://drive.google.com/open?id=0B-wSviYjd5oCZ3BTRHptOUtMbnM | 07:10.09 |
| kens | Give me a moment | 07:10.15 |
| psmlbhor | ok | 07:10.25 |
| kens | Your PostScript program doesn't request a media size | 07:11.23 |
| | So Ghostscript uses its default | 07:11.33 |
| | Most likely that is A4 or Letter (depending on your country) | 07:11.48 |
| | You are going to have to specify a media size to get this to work | 07:12.24 |
| psmlbhor | i had tried with sPAPERSIZE=a4 but it didn't work | 07:12.38 |
| kens | That's because A4 is already the default size | 07:12.49 |
| | You need *much* bigger media | 07:12.56 |
| psmlbhor | how can I achieve that? | 07:13.15 |
| kens | The content is scaled up by a factor of 4958x7017 | 07:13.26 |
| psmlbhor | yes | 07:13.31 |
| kens | The Bounding Box is given as that size (NB bounding boxes are comments and so are ignored) | 07:13.54 |
| psmlbhor | yes, but I have used scale command to stretch to that value | 07:14.32 |
| | Should I scale down it? | 07:14.40 |
| kens | So you need to add something like -dDEVICEWIDTHPOINTS=4958 -dDEVICEHEIGHTPOINTS=7017 | 07:14.46 |
| | Or, of course, add a media size request to the PostScript program | 07:15.18 |
| psmlbhor | with the suggested options it worked! | 07:15.35 |
| kens | OK that's good | 07:16.11 |
| psmlbhor | How can I add media size request to the PS file? Is there any option/command ? | 07:16.50 |
| kens | You should use the PostScript operator :-) | 07:17.10 |
| psmlbhor | OK. I will search for it | 07:17.34 |
| kens | In this case setpagedevice with a dictionary containing /PageSize [x y] where x and y are the widht and height of the media | 07:17.39 |
| | If you are going to program in PostScript you should Google for the PostScript Language Reference Manual and download a copy | 07:18.08 |
| psmlbhor | I will add that now. | 07:18.16 |
| kens | 3rd edition | 07:18.17 |
| psmlbhor | I already have a copy and I was able to generate that PS file after referring to that manual. But sometimes I get stuck | 07:18.44 |
| kens | Ah, OK if you have the manual then look at the section on selecting media | 07:19.03 |
| psmlbhor | OK. I will do that. | 07:19.24 |
| | kens, Thank you for all your help | 07:19.31 |
| kens | Section 6.1.1 "Page Device Dictionary" | 07:19.41 |
| | Starts on page 408 of my copy | 07:19.56 |
| psmlbhor | yes, found it | 07:20.19 |
| | Thanks once again | 07:20.33 |
| kens | NP Good luck ! :-) | 07:20.41 |
| remi__ | Hi, i'm using mupdf for an android project, the integration was easy and the viewer is really cool. i've encountered a small issue when i stress the viewer on big pdf in swipping left/right pages, i get an error Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 10647 (GCDaemon). is it a knowed issue ? annyway thanks for your great work | 10:06.43 |
| kens | Hi remi__ We've just had a company staff meeting and people are still travelling, so you may need to wait a while for a reply. I suspect its not a known problem as these tend ot get fixed quickly. However, someone who know more than me about MuPDF would probably need to ask you some questions about your project before being able to help | 10:09.34 |
| | I'd suggest you pop back in a day or two and ask again, or look at the logs to see if one of the MuPDF engineers replies | 10:10.07 |
| jogux | remi__: Can you reproduce the problem in the official mupdf google play app? | 10:13.02 |
| | remi__: and can you share the full android logcat output when the problem happens, using a site like http://pastebin.com ? Include as much output as possible, even if you're not sure if it's relevant. | 10:14.43 |
| sebras | jogux: remi__: it may also be useful for us to get the .pdf-file with which your saw the problem. if you have to possibilty to share it. | 10:21.32 |
| jogux | is working on a few improvements for the mupdf ObjC APIs btw (in the background whilst bored at the meeting, but also found a crash Robin is looking at). | 11:37.14 |
| Robin_Watts | So, I'm an idiot. | 12:06.39 |
| jogux | d'oh :-) | 12:09.54 |
| Robin_Watts | jogux: So, on robin/master, there is your commit, plus the next 3, all of which are dead simple fixes. | 12:10.04 |
| jogux | right, let me try those | 12:10.17 |
| Robin_Watts | oh, tor8 is here. Are you working today? | 12:10.20 |
| tor8 | Robin_Watts: the 4 commits on robin/master LGTM | 12:10.43 |
| | it's our national day thingy, but I figured I'd work a little bit | 12:10.59 |
| jogux | latest commit I see on robin/master is from 31st May? | 12:11.01 |
| | oh, wait, I see newer ones too | 12:11.23 |
| tor8 | jogux: ignore the commits after the WIP on robin/master | 12:11.36 |
| jogux | got it | 12:11.47 |
| Robin_Watts | pops to shop to forage for food. | 12:12.04 |
| tor8 | Robin_Watts: 4 commits on tor/master for review when you get back | 12:12.14 |
| Robin_Watts | tor8: Ta. | 12:12.21 |
| jogux | Robin_Watts: awesome, tested, no more crahses. | 12:19.04 |
| Robin_Watts | thanks. | 12:25.01 |
| | tor8: your 4 lgtm. | 12:26.47 |
| | Thanks for the reviews. | 12:26.54 |
| Robin_Watts | grabs some lunch. | 12:27.00 |
| tor8 | Robin_Watts: two more fixes on tor/master | 13:14.58 |
| Robin_Watts | tor8: lgtm | 13:26.51 |
| tor8 | Robin_Watts: alphabits should really be part of the draw device, IMO | 13:31.43 |
| Robin_Watts | alphabits? | 13:31.52 |
| tor8 | the anti aliasing level | 13:31.57 |
| Robin_Watts | You mean, move it out from the aa context into the device ? | 13:32.29 |
| tor8 | yes. | 13:32.33 |
| Robin_Watts | I have no objection to that beyond inertia. | 13:32.53 |
| | no strong objection at least. | 13:33.01 |
| tor8 | I am adding a fz_draw_options struct, and fz_parse_draw_options and fz_new_draw_device_with_options for muconvert use | 13:33.12 |
| | that can be used for all 'raster' output devices | 13:33.33 |
| Robin_Watts | tor8: OK, that makes sense. | 13:33.36 |
| tor8 | not sure how to handle banding though | 13:34.07 |
| | if that's something we want to bring into muconvert (and the document writer api) | 13:34.26 |
| | I expect we could do it by making it use the display list and then render in bands | 13:34.50 |
| kens | tor8, Robin_Watts Bug #696822 does seem to be real. Not so much that MuPDF offers to save a broken file after its repaired, but the saved copy is also broken.....So I reopened it | 13:34.56 |
| | I didn't check the HEAD code though, just the last release | 13:35.13 |
| Robin_Watts | kens: Ok, thanks. | 13:35.27 |
| jogux | I thought there'd been a decision to suppress the 'save?' dialogue when the user hadn't made any changes. or am I misremembering? | 13:36.27 |
| kens | Umm, no idea, could be a later change ? | 13:36.44 |
| Robin_Watts | jogux: Not for broken files, AIUI. | 13:36.55 |
| kens | I guess I could try more recent code... | 13:36.55 |
| jogux | ah | 13:37.01 |
| Robin_Watts | I think possibly for files where javascript runs and changes stuff. | 13:37.30 |
| jogux | that may be what I'm remembering | 13:37.48 |
| | oh, I have a file here that gets repaired again and again even if I tell it to save. | 13:38.01 |
| | that's on close as makes no difference to golden code. | 13:38.29 |
| kens | Sounds like its the same thing | 13:38.47 |
| Robin_Watts | So it's a real bug. :( | 13:38.51 |
| kens | I saved to a new fiklename and got the same error opening both files with GS | 13:38.59 |
| jogux | I'll add my file to the bug report as I guess it's probably same issue and the file I see it on is only 20K... | 13:40.49 |
| Robin_Watts | thanks. | 13:41.22 |
| | cd .. | 13:41.41 |
| jogux | okay, done | 13:43.22 |
| | hm, actually I don't remember where that file came from. could someone mark it as private please? | 13:44.22 |
| | ah. I can do that. bugzilla is just non-intuitive. | 13:45.20 |
| kens | It certainly is ;) | 13:45.27 |
| sebras | tor8: ping? | 14:23.03 |
| | tor8: I've tested luratech jbig2 vs jbig2dec now. | 14:23.23 |
| | tor8: turns out that for all files the fail in clusterpush I'm seeing a black rectangle with luratech instead of a white one with jbig2dec | 14:24.05 |
| | tor8: moreover a few images actually do render successfully with jbig2dec but are problematic with luratech. | 14:24.44 |
| HenryStiles | sebras: we need to report those, can you create bugs and assign them to me. | 14:26.14 |
| | ? | 14:26.20 |
| sebras | HenryStiles: sure, no problem. I'll retest with gs as well to make sure that I didn't mess up in the interface in mupdf. | 14:27.24 |
| | HenryStiles: do you want to to attach the files too? | 14:47.32 |
| | HenryStiles: they are in tests-private. | 14:47.39 |
| HenryStiles | sebras: file names are fine | 14:48.57 |
| sebras | HenryStiles: there are a few images where jbig2dec fails where luratech works fine. do you want me to report those too? | 14:51.11 |
| HenryStiles | sebras: we should already have bugs for those, no? | 14:55.33 |
| sebras | HenryStiles: only for one out of three. | 15:00.46 |
| HenryStiles | confusing jbig2 bugs are filed under either the jbig2 component or product | 15:01.07 |
| sebras | HenryStiles: I'll try to extract the jbig2data itself and place two bugs on the jbig2dec product. | 15:02.13 |
| chrisl | In theory, I think, bugs with the integration should be under "component" and bugs with jbig2dec should be under product - but it's hard to decide which a bug is in | 15:02.30 |
| HenryStiles | maybe marcosw knows why that is but it would be much nicer to have one category to search | 15:02.33 |
| | chrisl: that would be sane, yes | 15:03.30 |
| remi__ | Hi it's remi (again). i've post about a crash in android app this morning and i was asked to post the logcat. i've put it in http://pastebin.com/uHarZmGb. I made some test and i can't reproduce with the original mupdf android app so imust do something wrong.. | 15:04.36 |
| jogux | remi__: was there not any more logging after that? android usually prints out a stack trace in some form. | 15:05.27 |
| Robin_Watts | remi__: Were you building from git ? | 15:06.55 |
| remi__ | yes frop the git repository | 15:07.09 |
| Robin_Watts | I committed a fix this morning to the bitmap scaling code. | 15:07.14 |
| | It might be worth pulling and trying again. | 15:07.21 |
| remi__ | i've alreday did it | 15:08.02 |
| | i'm running the library from into a fragment | 15:08.27 |
| | i'm pulling it again just in case thank you | 15:09.12 |
| sebras | chrisl: I guess then we'd need a product for lura as well. | 15:10.05 |
| chrisl | sebras: I would say not, since it isn't our product | 15:10.59 |
| sebras | chrisl: true, but I thought about being consistent. :) | 15:11.36 |
| HenryStiles | sebras: putting it under component is fine. | 15:11.52 |
| sebras | HenryStiles: alright. | 15:12.19 |
| HenryStiles | the existing jpx/jbig that is | 15:12.32 |
| chrisl | sebras: if we wanted to be consistent that way, we'd have to have a product for all the third party libs, and that wouldn't make sense | 15:13.12 |
| HenryStiles | I'd vote for putting everything under one category but let's not fool with it now | 15:13.14 |
| nono_ | Hi | 19:20.16 |
| ghostbot | Welcome to #ghostscript, the channel for Ghostscript and MuPDF. If you have a question, please ask it, don't ask to ask it. Do be prepared to wait for a reply as devs will check the logs and reply when they come on line. | 19:20.16 |
| nono_ | I need to read music scores on an android tablet. I was planning to use mupdf as a base that I would hack into a score reader | 19:21.14 |
| | I can compile mupdf for linux but can't build it for android. I am trying right now and will provide the errors messages when they appear | 19:22.40 |
| | I am using debian jessie in virtualbox. I read the compile instructions, installed the 3rd libraries. I ran make generate at the root, then ndk-build in the platform/android/viewer folder | 19:54.34 |
| | Ok before compiling, a warning Android NDK: WARNING:jni/Android.mk:mupdfcore: LOCAL_LDLIBS is always ignored for static libraries. And the error [armeabi-v7a] SharedLibrary : libmupdf_java.so | 19:56.40 |
| | jni/../../../../source/fitz/printf.c:29: error: undefined reference to '__isinff' wich is followed b the same kind of errors. Any clue? | 19:56.40 |
| | Forward 1 day (to 2016/06/07)>>> | |
IRC Logs