LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Tue, 10 May 2005 12:25:02 +0200
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
From: Lars Hellström <[log in to unmask]>
In-Reply-To: <[log in to unmask]>
Content-Transfer-Encoding: 8bit
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Parts/Attachments: text/plain (28 lines)
At 10.19 +0200 2005-05-10, Achim Blumensath wrote:
>I agree that FD files should only contain font definitions. But for
>complex font families it can be quite cumbersome and error prone to
>write several dozens of FD files manually.

Who said FD files should be written manually? The base LaTeX FDs are
generated by docstrip, and the PSNFSS FD files are generated by fontinst,
to name two available tools. (Fontinst has no support for extra data,
though. At least not yet...)

>Since the font definitions of
>the MinionPro project are very regular we have created macros to
>generate them. So each FD file just consists of two lines. E.g.,:
>  \input{MinionPro-FontDef.sty}
>  \Mn@DeclareLargeFontFamily{T1}{MinionPro-OsF}{osf}{t1}
>But these macros rely on the keyval package which currently is included
>in a rather hackish way.

Keyval??? Seriously, I wouldn't be surprised if it would turn out to be
easier to do -- whatever it is you do -- directly in terms of TeX

Lars Hellström