| Summary: | karbon cannot open .eps on PPC | ||
|---|---|---|---|
| Product: | [Applications] karbon | Reporter: | Paolo Peruzzi <paolo> |
| Component: | general | Assignee: | Jan Hambrecht <jaham> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | error message with this file | ||
|
Description
Paolo Peruzzi
2006-06-26 09:47:07 UTC
Here's the output: $ karbon futura.eps parsing started state comment / unknown char ! (33) parsing aborted command to execute is (gs -q -P- -dBATCH -dNOPAUSE -dSAFER -dPARANOIDSAFER -dNODISPLAY ps2ai.ps '/home/pao/Eigene Dateien/Bilder/vector/futura.eps' | sed -e "s/%%BoundingBox: 0 0 612 792/%%BoundingBox: 0 0 0 0/g" > '/tmp/kde-pao/karbonkgDXkc.tmp') state comment / start char ! (33) parsing aborted does this happen with all EPS files? could you attach a sample file to this report for testing would be good if we could rule it the problem being PPC specific Created attachment 17495 [details]
error message with this file
Could not open.
Reason: Creation Error
Yes the ps import filter, or better our ps parser is lacking. That can be seen by these several open bugs about opening postscript files. Sadly we have not enough manpower nor time to fix that in the near future, at least not within the upcoming 1.6 realease. I hope to improve that by the time koffice 2.0 gets released. But i cannot promise anything as there is still so much work to be done. Ciao Jan Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone! Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |