The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 |
Newsgroups: comp.text.tex
From: Michael Zedler <Michael.Zed...@tum.de>
Date: Tue, 20 Dec 2005 17:02:55 +0100
Local: Tues, Dec 20 2005 11:02 am
Subject: Re: TTF2TFM
Paul Vojta schrieb:
> Now ttf fonts are 16-bit (at least), and Omega is 16-bit (at least), so To my knowledge, tfm are restricted to 8bit, thus ttf->tfm->ofm has an > I don't see why one would want to thread font access in Omega through > an 8-bit needle. 8bit bottleneck. > In a PostScript font, the strings "grave", "acute", etc. are the procedure Both correct. But. The glyph numbers in the tfm don't refer to the ttf > names for the glyph-drawing routines in the font. They are the primary > means for addressing the glyph routines. > In TrueType, however, glyph names (as I understand it) are optional. glyph index, but to an encoding vector, just like for PS fonts. (For mf fonts the "encoding vector" is implicit to the mf sources) If one of a) "tfm is 8bit" and b) "tfm point to positions in an encoding vector" don't hold, then yes, I see a need for ttf2tfm. >>> I can understand why ttf2afm is useful (i.e., for pdftex, since its ttf2pk is run to get the bitmap representation of the requested glyph. >>> font model is based on PostScript), but not for dvi creation. >> This is not correct, please have a look at how your dvi >> viewer/dvips/pdftex treat fonts. Neither is it related to the question >> ttf2tfm vs. ttf2afm+fontinst. > What exactly is not correct? > My dvi viewer (which is "mine" perhaps in a greater sense than you But the tfm is never read by the dvi viewer??? I don't see in what aspect a dvi viewer behaves differently from dvips (that is set up to use pk fonts). > dvips (at our site) handles ttf fonts in exactly the same way. Do you refer to my posting? There for sure a PS style encoding vector is > Look at another thread currently running on comp.text.tex to see how > dvips handles (or doesn't handle) ttf fonts. needed. BTW, is there hope that dvips will rather soon be extended to read ttf and otf, PLEASE? And to extend dvips that it can generate autoexpanded versions of tfm on the fly, just like pdftex? (I'm running pdftex in dvi mode with font expansion, this requires a massive number of tfm/vf in localtexmf)... > Yes, pdftex does use PostScript-style encoding files for ttf fonts, What else would you recommend? CID? Even if one used CID I don't see how > but I don't know any reasons for doing so other than for uniformity > with handling of PostScript fonts. to avoid encoding vectors, though (then its contents aren't glyph names but CID positions). > The OP (in a subsequent message) mentioned that s/he wanted to add see above, I'm curious to see 16bit tfm pointing directly to ttf glyph > OpenType (hence ttf) support natively in Omega. Therefore, my answer > above is framed in terms of what a good design would be, rather than > what is in place right now. indices. ;-) Best, You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| |||||||||||||