Summary: | ttc<->ttf fallback is expected for CJK font list in GlobalParamsWin.cc | ||
---|---|---|---|
Product: | poppler | Reporter: | suzuki toshiya <mpsuzuki> |
Component: | general | Assignee: | poppler-bugs <poppler-bugs> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | enhancement | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Windows (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
preliminary implementation of "ttc"<=>"ttf", "pfb"<=>"pfa" fallback
revised implementation of "ttc"<=>"ttf", "pfb"<=>"pfa" fallback revised implementation of "ttc"<=>"ttf", "pfb"<=>"pfa" fallback revised implementation of "ttc"<=>"ttf", "pfb"<=>"pfa" fallback |
Description
suzuki toshiya
2012-03-29 04:45:52 UTC
Created attachment 59347 [details] [review] preliminary implementation of "ttc"<=>"ttf", "pfb"<=>"pfa" fallback Here is preliminary implementation of "ttc"<=>"ttf", "pfb"<=>"pfa" fallback. This implementation is a reply to the post http://lists.freedesktop.org/archives/poppler/2012-April/008949.html In current framework of poppler, there is no distinction between the expected fonts (the exist of the font is expected, but the lack of the font is not irregular case) and the essential fonts (the lack of the font may cause serious problem in the font substitution). To reduce the warning to the lack of essential fonts, this patch introduces "warnIfMissing" boolean flag to displayFontTable[]. Created attachment 59373 [details] [review] revised implementation of "ttc"<=>"ttf", "pfb"<=>"pfa" fallback Tested and commented: http://lists.freedesktop.org/archives/poppler/2012-April/008960.html debug messages are removed. Created attachment 59374 [details] [review] revised implementation of "ttc"<=>"ttf", "pfb"<=>"pfa" fallback Previous patch is broken, here is corrected version. Created attachment 59376 [details] [review] revised implementation of "ttc"<=>"ttf", "pfb"<=>"pfa" fallback Commited. |
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.