xmlgraphics-fop-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremias Maerki <dev.jerem...@greenmail.ch>
Subject Re: FOP character mapping problems
Date Thu, 01 May 2003 08:26:08 GMT
On 25.04.2003 01:15:46 J.Pietschmann wrote:
> Clay Leeds wrote:
> > FMI: Is that like "regular", Bold, Italic, and Bold Italic?
> I've seen TTCs mainly for providing several writing styles, sort of,
> for e.g. chinese. The concept is not unlikely the concept of
> character slant in western scripts; it covers for example variations
> in line caps, line width changes along lines, gaps and bends. In such
> cases the fonts in the TTC have related but different names.
> Occasionally I've seen completely unrelated fonts in one TTC. I don't
> really know whether TTCs are just concatenations of TTFs with a common
> header or whether the fonts may share structures like code tables or
> glyph definitions. Jeremias will tell you.

Huh. I can't. I'm not yet that up-to-speed with TrueType fonts.

Here's a summary from the OpenType specification:

| A TrueType Collection (TTC) is a means of delivering multiple OpenType
| fonts in a single file structure. TrueType Collections are most useful
| when the fonts to be delivered together share many glyphs in common. By
| allowing multiple fonts to share glyph sets, TTCs can result in a
| significant saving of file space. 
| For example, a group of Japanese fonts may each have their own designs
| for the kana glyphs, but share identical designs for the kanji. With
| ordinary OpenType font files, the only way to include the common kanji
| glyphs is to copy their glyph data into each font. Since the kanji
| represent much more data than the kana, this results in a great deal of
| wasteful duplication of glyph data. TTCs were defined to solve this
| problem. 

Jeremias Maerki

To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org

View raw message