Till Kamppeter wrote:
Tobias, if this needs to be fixed in the texttopdf filter a bug on https://bugs.linuxfoundation.org/ can be filed. If it is a problem of Debian's packaging or Debian shipping a broken font or not shipping a required font then open a Debian bug.
Well, it's still not clear, who should fix what:
1. cups-pdf should probably announce that it can not only process PS, but also PDF. I'm not sure if the current cups-filter architecture handles this case well. This bug would be one of cups-pdf or cups-filter(?). 2. It's unclear to me what the policy regarding pdftops is wrt. to using popper vs. ghostscript as converting agent. gs generates Type 3 (which causes problems), poppler does not. This can be fixed in pdftops, i.e. cups-filter, (use poppler tools in this case), or ghostscript (don't generate Type 3 -- there might be some commandline switches) 3. The issue, that the Type 3 bounding boxes generated by ghostscript are deemed bad by poppler/evince. The experts from ghostscript and poppler have to determine who is wrong (it might even be caused by the original font file). Therefore this is either a poppler/evince, ghostscript or font bug.
I'm not sure if any of these points could even be worked around by texttopdf, i.e. no bug in textopdf, AFAICS. I don't have the spare time to take steps 1.-3. further myself, so if anyone would take over from here?
Tobias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
