You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by "John Cumming (JIRA)" <ji...@apache.org> on 2015/04/22 08:43:58 UTC
[jira] [Commented] (FOP-2460) Subsetting OTF font leads to PDF
errors when viewing / incorrect characters
[ https://issues.apache.org/jira/browse/FOP-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506533#comment-14506533 ]
John Cumming commented on FOP-2460:
-----------------------------------
We have also had problems with several other OTF fonts, including Adobe Caslon Pro Regular. We get a series of filled circles and no valid rendered glyphs in the output. Other applications, such as MS Word, FrameMaker and InDesign all handle the font OK.
This may well be a different problem but could be related ?
I have always assumed that the bug is somewhere in the OTF handling, although haven't had a look myself yet.
> Subsetting OTF font leads to PDF errors when viewing / incorrect characters
> ---------------------------------------------------------------------------
>
> Key: FOP-2460
> URL: https://issues.apache.org/jira/browse/FOP-2460
> Project: Fop
> Issue Type: Bug
> Components: font/opentype
> Affects Versions: trunk
> Reporter: Robert Meyer
>
> When attempting to generate a document whilst subsetting the VilleroyBoch-Regular.otf font, different viewers will either show errors, no text or lead to incorrect or corrupt characters being drawn.
> I currentlty believe this is down to either a subroutine not being copied from the original font leading to a invalid reference, or the subroutine does not contain valid data. When looking at this font in FontForge, 3 characters in a "hello world" example I used were missing which backs up this hypothesis.
> [EDIT] I've removed the font as I did not check if there were copyright issues by making it public domain. I will work when I am able to do so but keep the font privately unless I hear otherwise from the user who originally posted the problem
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)