Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Xmlgraphics-fop Wiki" 
for change notification.

The "AFPFonts" page has been changed by JeremiasMaerki.
The comment on this change is: Thoughts on necessary changes in FOP and 
pointers into the code.
http://wiki.apache.org/xmlgraphics-fop/AFPFonts?action=diff&rev1=1&rev2=2

--------------------------------------------------

+ = Notes on AFP Fonts =
+ 
- = Unicode Fonts in AFP =
+ == Unicode Fonts in AFP ==
  
  This section describes the necessary steps to support Unicode fonts in AFP. 
"Unicode fonts" in AFP jargon are outline fonts (CID Keyed font (Type 0)). They 
define their glyphs using GCUIDs (Graphic Character UCS Identifiers), for 
example "U0000061" for Unicode 0x0061 (LATIN SMALL LETTER A, "a").
  
@@ -16, +18 @@

  
  Finally, in PTOCA, the TRN data can simply be UTF-16BE encoded character data.
  
- That's it.
+ === Changes in FOP for Unicode Fonts ===
  
+ We need a new class that represents a "CID Keyed font (Type 0)". So far, we 
have support for bitmap fonts (!BitmapFont.java) and Type 1 outline fonts 
(!OutlineFont.java). For the new font type, we need another subclass for 
org.apache.fop.afp.fonts.AFPFont. Maybe OutlineFont can even be reused since 
the Unicode fonts are very similar to the normal outline fonts.
+ 
+ Until now, we only had single-byte encodings. The actual encoding of the 
characters happens in org.apache.fop.afp.fonts.!CharacterSet (the last few 
methods). For "T11200", the Java "UTF-16BE" encoding could be used (specified 
in the configuration as we don't build a character map from the codepage 
resource, yet, which would actually be cleaner and more versatile but take some 
more work to accomplish).
+ 
+ The coded font (BCF/ECF) is not implemented in FOP, yet. Maybe this whole 
thing here also works without a separate coded font. To date we combine font 
and codepage in the MCF. Not sure if this will still work for Unicode fonts but 
it is recommended to add support for BCF/ECF. The 
org.apache.fop.afp.modca.!MapCodedFont should be straight-forward and similar 
to a normal outline font.
+ 
+ For the PTOCA TRN data, this biggest difference is that we're no longer 
encoding EBCDIC data but UTF-16BE data.
+ 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to