Summary: | "Couldn't create a font" when opening a Korean PDF | ||
---|---|---|---|
Product: | poppler | Reporter: | Sebastien Bacher <seb128> |
Component: | general | Assignee: | poppler-bugs <poppler-bugs> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | high | CC: | mdke |
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
English PDF with embedded truetype fonts
another example |
Description
Sebastien Bacher
2006-10-01 06:07:29 UTC
Note that this bug isn't just with Korean fonts, it applies to any PDF I've tried with embedded truetype fonts. I'll attach an English one. Created attachment 7225 [details]
English PDF with embedded truetype fonts
As promised, here is the attachment.
Created attachment 7633 [details]
another example
this is still a problem on Ubuntu feisty, which sports libpoppler 0.5.4. Any news? Some font fixes just went into poppler head. If possible, can you test again with that configuration? Even confirming if it is still a problem with poppler 0.6.2 would be useful. Using libpoppler 0.6.2 - the description example doesn't open in evince, it's using over 1.6G in tmp and breaking due to the lack of space there - the desktopguide.pdf example is still displayed empty and "some font thing failed" lines are written on the command line - using test-poppler-glib displays identic "some font thing failed" warnings I finally got around to trying this with Qt4 tools on top-of-tree. Still bad. "Couldn't create a font for" errors are due to FreeType erroring on loading some font, i reported the problem to them and they said the fonts are broken and will not support them. Sorry there's nothing more i can do. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.