[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=15179377#comment-15179377 ] chunlinyao commented on FOP-2460: - I'd like to provide a TestCase, OTFSubSetFileTestCase.java seems OK but the getFullCharString logic in it is not correct. I need a OTF font use hints and subroutines heavily to test. Noto Sans CJK is over 15M. > 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)
[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=15177722#comment-15177722 ] Matthias Reischenbacher commented on FOP-2460: -- I can confirm that your patch for FOP-2557 fixes also this issue. Nice work chunlinyao! Robert, could you do a review of the patch? chunlinyao: if you could add a test case (similar to OTFSubSetFileTestCase.java), it would be perfect. > 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)
[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=15176838#comment-15176838 ] chunlinyao commented on FOP-2460: - [~rmeyer] can you confirm is this issue resolved by a patch in FOP-2557 > 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)
[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)
