Re: Italic open-o in omega - metrics etc

See below. 

As VladimirVolowich described, that is what I did with the Chinese TTF font I 
started with. 

But I also created a 'level-1' OPL file to go with it. The metrics in 
there, defined for the whole unicode font are applied by OMEGA. 

This allows 'font-wide' kerning, ligatures to be defined once for the 
whole font, even though it has been broken down into subfonts.

Cheers

From: Roger P Wright
Please don't send me emails with HTML in. My spam filter will reject them.
Read this if you don't know if your email settings are 'plain text' or 
not: http://support.pinehurst.net/email/nomime.html 




Alexej Kryukov <akrioukov@xxxxxxx>
Sent by: omega-admin@xxxxxxxxxxxxxxxxxxxxx
31/05/03 14:12

 
        To:     Danilo Segan <dsegan@xxxxxxx>, Omega list 
<omega@xxxxxxxxxxxxxxxxxxxxx>
        cc: 
        Subject:        Re: [Omega] Italic open-o in omega


On Saturday 31 May 2003 16:39, Danilo Segan wrote:
>
> As Yannis already explained, kerns, ligatures, and all the metric
> data are "consumed" by TeX/Omega, and therefore, they're used
> correctly.
>
> The separation to smaller files is done on the last processing step
> when PostScript needs to be produced (it allows font mappings which
> contain at most 255 or 256 charname -> glyphs mappings). So, this
> step and technique is only used for outputing the *glyphs* on already
> established spots (by TeX, which did use kerning and other
> information from VF to determine them).
>
> On the other hand, you might be talking about manually breaking one
> big font to smaller fonts, with each having a separate metric file
> (instead of VF which can "join" several fonts; one might also need to
> use OVF, right?). This would be a bad solution, but it is not used,
> so I guess there's no need to fear :-)

My message was an answer to the message posted by Vladimir 
Volowich, who proposed the following sequence:

a) We create a set of TFM files, each of them refers to a subset
of "big" ttf or pfb file. Of course, each TFM file contains kerning
information only for glyphs it includes.

b) We join glyphs from these subsets to a Unicode virtual font
having the OVF extension. Such a font needs also a corresponding
metric file (with OFM extension). As you can see,  only kerning
information already present in the TFM files may be preserved,
of course, unless we want to edit the source OVP file manually.

That's why I said this method doesn't look very good and logical.
However, this is the only working method to install Unicode ttf or pfb
fonts for Omega *right now*.

_______________________________________________
Omega mailing list
Omega@xxxxxxxxxxxxxxxxxxxxx
http://omega.cse.unsw.edu.au/mailman/listinfo/omega

smime.p7s
Description: S/MIME Cryptographic Signature