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
 
Michael Zedler  
View profile  
 More options Dec 16 2005, 4:13 pm
Newsgroups: comp.text.tex
From: Michael Zedler <Michael.Zed...@tum.de>
Date: Fri, 16 Dec 2005 22:13:26 +0100
Local: Fri, Dec 16 2005 4:13 pm
Subject: Re: TTF2TFM
Print | View thread | Show original | Report this message | Find messages by this author
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.

> 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.

> 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.

Michael


 
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