Sorry, I haven't spoken, read or written German since I was at school! But Google translate did a good enough job to get the idea of what they said and, frankly, I strongly disagree with what they say.
What they have written implies that they have not actually analysed the Postscript you have sent, they have simply looked at the error message, and replied based on that. Valid Postscript adheres to a standard (written and published by Adobe), and whilst various companies have their own additional customisations, the core language must adhere to the standard or it is not valid Postscript. I have access to six different Postscript implementations: Adobe Distiller, Global Graphics Harlequin, Global Graphics JaWS, a Postscript implementation also from Kyocera(!!), Ghostscript (of course!), and with sufficient prior arrangement, Adobe CPSI. All the above run your file to completion without errors or warnings (including the Kyocera one). In addition, I've looked fairly carefully at the Postscript myself, and I see no problems with it. Based on the above, the Opera Postscript output is valid, correct Postscript, and the bug is with the printer. FWIW, I am quite happy for you to quote me on that, or even to follow up with Kyocera Germany on your behalf (assuming they can accept e-mails in English!). There is almost no point trying to compare the Postscript produced by different applications - Postscript is a turing complete programming language, as well as page description language, there are, therefore, an almost infinite number of totally different ways a given page can be represented. It's *highly* unlikely you (or anyone) will be able to look at the two sets of output, and pin-point the cause of the problem. The only way to narrow down the problem is, as I described before, for someone like me to hand edit the Postscript, progressively cutting it down, and possibly "instrumenting" it, so that you can try the each iteration on your printer, until we reach the one thing (or set of things) that causes the problem. It is a laborious process, that takes time, paper and toner, but it really is the only option. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1263415 Title: Kyocera FS-1100D cannot print Google Maps - limitcheck --image-- Status in “cups” package in Ubuntu: Confirmed Bug description: I'm trying to print a simple page from Google Maps (including the big map provided) - but I have this problem with a couple more files here as well. I always get error: Error Name: /limitcheck Offending Command: --image-- Operand Stack: Printer: Kyocera Mita FS-1100D, I'm using the vendor provided ppds. I tried cups-filters Version: 1.0.18-0ubuntu0.1 Version: 1.0.17-0bzr0.1 both were not resolving the matter (see cups-filters bug 982675). I know this used to work some time ago, but it isnt anymore. On the other hand, I'm having a WinXP-VM on this machine and it can print the file w/o any troubles. I attach cups error_log (LogLevel debug) and the captured print data. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cups 1.5.3-0ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-57.87-generic 3.2.52 Uname: Linux 3.2.0-57-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sun Dec 22 00:06:18 2013 InstallationMedia: Kubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2) Lpstat: device for Canon_iP5200: http://localhost:1631/printers/Canon_iP5200 device for FS-1100: usb://Kyocera/FS-1100 device for MFC-9100c: socket://192.168.0.198:9100 device for PDF: cups-pdf:/ MachineType: LENOVO 6460DAG MarkForUpload: True Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-57-generic root=UUID=b3c4885b-0279-464f-aa1d-ade5ab9f328b ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to precise on 2012-09-02 (475 days ago) dmi.bios.date: 11/14/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC5WW (2.25 ) dmi.board.name: 6460DAG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC5WW(2.25):bd11/14/2008:svnLENOVO:pn6460DAG:pvrThinkPadT61:rvnLENOVO:rn6460DAG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6460DAG dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO mtime.conffile..etc.cups.cupsd.conf: 2013-12-21T23:50:08.489281 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1263415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
