Bug 1061161 - Cairo generates PDFs with wrong font names
Summary: Cairo generates PDFs with wrong font names
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: cairo
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Benjamin Otte
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-04 13:12 UTC by Marek Kašík
Modified: 2015-06-29 14:59 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 14:59:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
reproducer (6.08 KB, application/pdf)
2014-02-04 13:12 UTC, Marek Kašík
no flags Details


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 73441 0 None None None Never

Description Marek Kašík 2014-02-04 13:12:59 UTC
Created attachment 859136 [details]
reproducer

Description of problem:
Cairo exports font names in their original form. But these can be wrong, they can sometimes contain white space characters or PDF/PostScript delimiter characters. Such fonts are not common but they appear.

This can cause a problem when you are printing such file in evince. The printing fails during processing of an intermediate PDF because there are delimiter characters where they shouldn't be.


Version-Release number of selected component (if applicable):
cairo-1.13.1-0.1.git337ab1f.fc20


How reproducible:
Always


Steps to Reproduce:
1. run "pdftocairo -pdf test-cff.pdf result.pdf"


Actual results:
Font names in result.pdf contain white-spaces characters and delimiter characters.


Expected results:
Font names in result.pdf don't contain white-spaces characters and delimiter characters.


Additional info:
Fix was already pushed upstream, see https://bugs.freedesktop.org/show_bug.cgi?id=73441.

Comment 1 Fedora End Of Life 2015-05-29 10:48:18 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-06-29 14:59:33 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.