| | <<<Back 1 day (to 2018/10/29) | 20181030 |
| lorfds | hey peeps anyone home | 08:31.03 |
| | im trying to get a pcl 5 file to convert to pdf correctly | 08:31.14 |
| kens | That may not be possible unless you render it | 08:31.25 |
| lorfds | almost everything works right but i think the font set is incorrect | 08:31.38 |
| | what does it mean to render it? | 08:31.46 |
| kens | Turn it into an image | 08:31.55 |
| | a bitmap | 08:31.59 |
| lorfds | how would i do that? | 08:32.07 |
| kens | Well it doesn't sound like this is your problem, so you don't want to | 08:32.29 |
| | But we're going to need to see the inptu file before we can say for sure | 08:32.52 |
| | So your best bet is to open a bug report, attach the PCL file there and supply the command line you are using | 08:33.15 |
| | You can also use the display device to viiew what the original PCL looked like, if that's wrong then the PDF otuput will likewise also be wrong | 08:33.59 |
| lorfds | where's the display device? | 08:34.30 |
| kens | Built into the executable, just like all the devices | 08:34.47 |
| | if you do "gs --help" you'll get a list of them | 08:35.10 |
| lorfds | oh....will the display device output a file? | 08:35.16 |
| kens | No, it will draw the output on the display, hence the display device | 08:35.29 |
| | You can use one of the other devices to create an image file | 08:35.40 |
| lorfds | so i need to be running x-windows to see the display device? | 08:36.05 |
| kens | Ah so you'r eon Linux. | 08:36.22 |
| lorfds | yeah | 08:36.30 |
| kens | In that case you do need X | 08:36.31 |
| | Or you can render to a file and look at that | 08:36.44 |
| | PNG, JPEG, PBM etc | 08:36.54 |
| lorfds | ahhh...so that is just like display device? | 08:37.06 |
| kens | The 'high level' devices preserve vecrtor input as far as possible, all the other devices render to a bitmap. The difference between them are in what kind of bitmap they create (colour model etc) and the file format they write. | 08:37.54 |
| | So the display device writes to the display, teh PNG devices write PNG files, the TIFF devices write TIFF files, etc | 08:38.20 |
| lorfds | @kens: so the image file output looks correct...what does this mean for my pcl to pdf conversion? why isn't it outputting correctly? | 09:20.08 |
| kens | Then that means the problem is pdfwrite, not the PCL interpreter | 09:20.24 |
| | Without seeing the file I can't possibly comment on what could be wrong | 09:20.37 |
| lorfds | well, what are likely suspects with pdfwrite? | 09:21.05 |
| | would bad font be a problem? | 09:21.11 |
| | or missing font? | 09:21.20 |
| kens | The most likely provlem is Raser OPs, which cannot be represented in PDF | 09:21.26 |
| | Raster* | 09:21.30 |
| | But that's unlikely to affect fotns. | 09:21.43 |
| | I can think of nothgin likely to cause a font provlem if the file renders correctly otehrwise | 09:21.56 |
| lorfds | can raster ops be fixed? | 09:22.14 |
| kens | No, its a fundamental incompatibility in the graphcis models of PCL and PDF. PDF doesn't' support RasterOps, and they cannot be represented in a PDF fiel without rendering the page to an image. | 09:22.55 |
| | But as I say, that's not likely the problem with text. I can't really give you any information without seeing teh input file. | 09:23.34 |
| | Forward 1 day (to 2018/10/31)>>> | |
Log of #ghostscript at irc.freenode.net.