Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
comp.text.tex
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion TTF2TFM
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
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Paul Vojta  
View profile  
 More options Dec 20 2005, 3:54 am
Newsgroups: comp.text.tex
From: vo...@math.berkeley.edu (Paul Vojta)
Date: Tue, 20 Dec 2005 08:54:22 +0000 (UTC)
Local: Tues, Dec 20 2005 3:54 am
Subject: Re: TTF2TFM
Print | View thread | Show original | Report this message | Find messages by this author
In article <dnvalm$1b...@wsc10.lrz-muenchen.de>,
Michael Zedler  <Michael.Zed...@tum.de> wrote:

>Paul Vojta schrieb:
>> In article <dnu2op$ar...@wsc10.lrz-muenchen.de>,
>> Michael Zedler  <Michael.Zed...@tum.de> wrote:
>>> I never quite understood what's the advantage of ttf2tfm over
>>> ttf2afm+fontinst.

>> Well, TeX uses numbers and not names to refer to glyphs.
>> Ttf also uses numbers and not names to refer to glyphs.

>Please have a look at what role encodings play, for TTF t1-wgl4.enc is
>of particular interest.

OK, let's look at t1-wgl4.enc.  First of all, there's the line:

        /T1Encoding [           % now 256 chars follow

Now ttf fonts are 16-bit (at least), and Omega is 16-bit (at least), so
I don't see why one would want to thread font access in Omega through
an 8-bit needle.

Next there's the line:

          /grave /acute /circumflex /tilde

In a PostScript font, the strings "grave", "acute", etc. are the procedure
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.

>> If you use ttf2afm, you have to assign names to your glyphs so that they
>> can be removed by afm2tfm.  Sounds kind of pointless to me.

>I referred to fontinst, not afm2tfm. The former is quite useful to
>generate T1/TS1 encoded fonts as well as to correct kerning flaws.
>For the user who is mainly interested in a quick installation the most
>obvious advantage is the automatic generation of fd+map files.

OK, so the names are removed by fontinst instead of by afm2tfm.

>> I can understand why ttf2afm is useful (i.e., for pdftex, since its
>> 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
anticipated) is xdvi (non-k).  It is set up to treat ttf fonts via
mktexpk, which calls ttf2pk (a program related to ttf2tfm).  It does not
use tfm files directly.

dvips (at our site) handles ttf fonts in exactly the same way.
Look at another thread currently running on comp.text.tex to see how
dvips handles (or doesn't handle) ttf fonts.

Yes, pdftex does use PostScript-style encoding files for ttf fonts,
but I don't know any reasons for doing so other than for uniformity
with handling of PostScript fonts.

The OP (in a subsequent message) mentioned that s/he wanted to add
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.

I have no objections to encoding files per se, but enc files in the
style of t1-wgl4.enc were designed for PostScript fonts, and are not
well suited for use with ttf fonts.  If one uses encoding files with
ttf fonts at all, they should be in a ttf-specific format.  However,
I don't see a need for them, since TrueType fonts already contain an
encoding.  If you don't like the encoding, then use a virtual font.
Of course, the encoding is 16-32 bits wide, but Omega can handle that.

--Paul Vojta, vo...@math.berkeley.edu


 
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.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google