> On 29 Nov 2015, at 15:28, Glenn Adams <[email protected]> wrote: > > On Sun, Nov 29, 2015 at 3:05 AM, Andreas L. Delmelle (JIRA) <[email protected]> > wrote: > > [ > https://issues.apache.org/jira/browse/FOP-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15030875#comment-15030875 > ] > > Andreas L. Delmelle commented on FOP-2540: > ------------------------------------------ > > > In the other direction, it would likely be very rare situations. I cannot > immediately think of use cases for mapping a single codepoint to more than > one glyph...? > > The function of CMAP is not involved in these types of mappings; rather, the > GSUB table is used. And, BTW, there are many examples of M to N mappings (M > != N). See org.apache.fop.complexscripts.fonts.GlyphSubstitutionTable for > examples.
Of course... It occurred to me after having written that comment that there are indeed many examples. The most common ones are letters w/ various accents or diacritical marks, where the glyph for the letter and the one for the accent can be separated in the font. At any rate, that would indeed be more a complex scripts function, so should already be supported. Will still take a look at correcting the situation for mapping different codepoints to the same "8-bit" glyph then, since that definitely does not seem to be functioning properly at this point. BTW - Hope someone in the meantime can already try out the patch on Linux, and see if the support for OTFs is also improved there. I suppose a similar situation exists on that platform, i.e. not all of the system fonts having a Windows/Unicode cmap... KR Andreas
