[ https://issues.apache.org/jira/browse/PDFBOX-5808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17841241#comment-17841241 ]
Fabrice Calafat commented on PDFBOX-5808: ----------------------------------------- That's a good point. Indeed, the flag I added is to disable all, which I think can be useful if we cannot control per GSUB features As for the example, unfortunately the font I'm using for testing is proprietary and cannot be shared: [https://creativemarket.com/PeachCremeFonts/2055357-Adora-Bouton-Luxury-Script.|https://creativemarket.com/PeachCremeFonts/2055357-Adora-Bouton-Luxury-Script] > Add support for GSUB Lookup Type 3 > ---------------------------------- > > Key: PDFBOX-5808 > URL: https://issues.apache.org/jira/browse/PDFBOX-5808 > Project: PDFBox > Issue Type: New Feature > Components: FontBox > Affects Versions: 3.0.2 PDFBox > Reporter: Fabrice Calafat > Priority: Major > Attachments: screenshot-1.png, screenshot-2.png > > > Add support for the lookup type 3, Alternate Substitution when handling GSUB: > [https://learn.microsoft.com/en-us/typography/opentype/spec/gsub#AS] > The first available substitution glyph can be used (as done in other > libraries) > > Also, the current implementation of CompoundCharacterTokenizer doesn't > account for collision in ligatures > For example, if a font supports ligatures for _att_ and {_}en{_}, the current > implementation will not tokenize properly for the word _attention._ This is > because the regex implementation doesn't allow for a proper split > > I'll open a proposed implementation for the above -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org