| | <<<Back 1 day (to 2013/08/31) | 2013/09/01 |
| blaaa | Using postscript as PDFtoPS in cups generates code on with my printer (PagePro 1250E) chokes. a PS file generated with Mac OS X Quartz (and cups, same PPD) works just fine. | 08:31.37 |
| | The output generated by poppler results in ASCII (apparently PS code of some sort I suppose) printed in a staircase pattern | 08:31.41 |
| | Should I provide some test output? | 08:49.03 |
| sebras | blaaa: you may have to wait for an answer. the ghostscript devs are here mostly during working hours, so they are probably back tomorrow. sometimes they do answer questions during weekends though. | 10:38.36 |
| blaaa | sebras: thanks for the info | 10:39.56 |
| | sebras: ill try to stay around for a few days, dont know if its possible though | 10:40.50 |
| | but i suppose I can read he log and respond | 10:41.22 |
| Robin_Watts | blaaa: Your best bet is maybe to create a new bug at bugs.ghostscript.com | 10:46.54 |
| | Attach the PDF file you are starting with. | 10:47.04 |
| | attach the PS file you get. | 10:47.21 |
| | I suspect you'll need to talk to kens/chrisl about this though, so hanging around here for 24 hours would be good. | 10:47.57 |
| | They will probably want to know if you can cause the same problem by just calling ghostscript without involving cups. | 10:48.24 |
| | If not, they may refer you to tkampeter to get the exact gs command line that cups calls. | 10:48.55 |
| blaaa | Robin_Watts: thanks I'll take a look at the bug report and look for them. The strange thing is that poppler output does not work as well, which makes me wonder what part of the whole setup of pod,cups,gs/poppler,printer is to blame | 10:49.08 |
| Robin_Watts | In previous cases they've worked with people with problem printers to produce cut down files to isolate the problem. | 10:49.42 |
| blaaa | Maybe the printer's PS2 emulation is just bugy which had not been an issue before or on mac os x | 10:49.44 |
| Robin_Watts | often it's a bug in that particular printer. | 10:49.59 |
| blaaa | Robin_Watts: that would not surprise me in this case | 10:50.30 |
| | It's a rather cheap&old printer | 10:50.41 |
| | Miht just replace it, but I don;t print as much anymore, so that's a bit wasteful | 10:51.08 |
| chris_99 | am i being very stupid or does MuPDF only write the XML data from the pdf to stdout, rather than passing it back to the calling function | 13:42.20 |
| Robin_Watts | chris_99: The text extraction device returns C structures with blocks/lines/spans/chars in. | 13:43.46 |
| | The code that converts that to XML only writes to stdout. | 13:44.03 |
| | The code that converts to XML is just an example of what can be done. | 13:44.22 |
| chris_99 | aha, what file is the text extraction device in? | 13:44.51 |
| Robin_Watts | source/fitz/stext-device.c | 13:45.26 |
| chris_99 | ah that's great thanks | 13:46.11 |
| Robin_Watts | See the if (showtext) section in mudraw.c in the drawpage function for how to call it. | 13:46.26 |
| chris_99 | oh i get it now thanks, i can just write my own function like in source/fitz/stext-output.c | 14:05.15 |
| | Forward 1 day (to 2013/09/02)>>> | |
IRC Logs