| | <<<Back 1 day (to 2017/10/20) | 20171021 |
| TwisteR | hi all! Is it possible to post-process all the images inside PDF using external tools? E.g. 1) extract all the images from PDF 2) process them somehow (without changing size) 3) put them back? | 03:05.32 |
| | step 1 already done with 'pdfimages' tool | 03:06.05 |
| | so, basically, the question boils down to step 3 | 03:06.53 |
| | preferably, via gs | 03:07.27 |
| kens | TwisteR : Its technically possible, but would be difficult to do in practice. I wouldn't even attempt to use Ghostscript. The only way that the images are going to be the same size after processing is if they are stored uncompressed in the PDf file. If they cahnge by even a single byte, then you will need to regenerate the xref table. If I were doing this I would write a tool in C to do it. NB the PDF 1.5 use of compressed xrefs | 07:41.41 |
| | would make this a still more difficult task. | 07:41.41 |
| | It would be possible (but still a lot of work) to modify the pdfwrite device and insert an image processing filter device to process the images as they are interpreted. Then pass the modified data to the pdfwrite devcie which would assemble it into a new PDF file. You could also do similar trick with MuPDF I believe. | 07:43.27 |
| TwisteR | kens: thank you for details! I got the general idea | 08:35.06 |
| kens | No problem | 08:35.13 |
| istankovic | hello | 17:58.50 |
| ghostbot | Welcome to #ghostscript. 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. If you are looking for help or infomation about MuPDF, try the new #mupdf channel. | 17:58.50 |
| istankovic | I am having trouble printing a Korean text on my Lexmark E260d printer | 17:59.21 |
| | the driver I'm using is Postscript-Lexmark from https://www.openprinting.org/printer/Lexmark/Lexmark-E260d | 18:00.25 |
| | worked fine so far | 18:00.41 |
| | however, now when I try to print a simple Korean text (no graphics), I get an error and a PS stack trace | 18:01.41 |
| | funny thing is, the first line is actually printed correctly | 18:01.54 |
| | and then the error is printed: ERROR: invalidaccess OFFENDING COMMAND: ] | 18:02.40 |
| | as far as CUPS is concerned, printing seems to work fine | 18:03.46 |
| | I'd appreciate any help with this as I am not that familiar with the whole printing stack | 18:05.45 |
| | Forward 1 day (to 2017/10/22)>>> | |
Log of #ghostscript at irc.freenode.net.