xmlgraphics-fop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 51144] New: ToUnicode table for subset font contains invalid entries
Date Tue, 03 May 2011 11:08:59 GMT

             Bug #: 51144
           Summary: ToUnicode table for subset font contains invalid
           Product: Fop
           Version: 1.0
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: fonts
        AssignedTo: fop-dev@xmlgraphics.apache.org
        ReportedBy: r.grosmann@gmail.com
    Classification: Unclassified

In the ToUnicode table that maps character codes from a subset font to unicode
characters, the first three entries map to unicode <ffff>. The first one is the
.notdef glyph, so this is OK, but the following two might be incorrect.

This is the beginning of such a table:

21 beginbfchar
<0000> <ffff>
<0001> <ffff>
<0002> <ffff>
<0003> <002d>
<0004> <0031>

I posted a question on the fop-users mailing list on 2 may 2011.  Mehdi
Houshmand replied on 3 may 2011:

Yes this is a bug, which has been fixed in my patch, but since I
didn't think anyone else had bumped into it I didn't want to put it
into trunk since I also made some code improvements to the class and
was weary that it could cause merge issues when/if the branches are

The issue is that in most fonts the first 3 glyphs are set to .notdef,
and this was implemented in FOP. However, the spec says only the first
glyph is reserved for .notdef, and what happens in MOST fonts doesn't
happen in ALL fonts.

Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

View raw message