--- Comment #1 from Jeremias Maerki <[EMAIL PROTECTED]>  2008-10-30 11:05:46 
PST ---
I'm happy to read that you're willing to jump in. So I'm happy to offer some
pointers in the hope that they help you.

For specifying which fonts should be referenced rather than referenced, see:
In the case of TrueType fonts, the referenced font is currently defaulting to
WinAnsi encoding (8-bit). You can see that in TTFFontLoader. A SingleByteFont
instance is created rather than a MultiByteFont instance. The TTFFontLoader is
responsible to load the font and make it available (metrics, glyph widths,
kerning pairs etc.). MultiByteFont is currently always in "font subset" mode.
It doesn't know anything else. I suspect that you might need to subclass
MultiByteFont into two implementations: one for subsetting and one for a fixed
CID set. Maybe you can also reuse MultiByteFont's parent class CIDFont to a
certain degree. You will, of course, also need CMaps. We can probably use the
same files as PDFBox (incubating, see [1]). Legal recently approved their use
inside the ASF. One problem is to select the right CMap. I'm not sure but maybe
that information could be in the TrueType file itself.

You won't get around looking into the PDF 1.4 specification (chapter 5) [2] and
the OpenType/TrueType specification [3].

Just a few hints on the procedural side: Please don't use tab characters in the
Java sources and try to mimic the original code style. We will need you to
submit a signed ICLa (and a CCLA if necessary) [4] before we can apply any
non-trivial patches from you. Please don't forget to update the documentation
(src/documentation directory) if you add any noteworthy functionality (other
users will be grateful). More information on the FOP and ASF websites. Don't
hesitate to ask for help if anything's unclear. Development-related discussions
preferably on the fop-dev mailing list.



Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to