LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

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

Print Reply
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
From: David Carlisle <[log in to unmask]>
Date: Tue, 10 May 2005 10:07:47 +0100
In-Reply-To: <[log in to unmask]> (message from Achim Blumensath on Tue, 10 May 2005 10:19:21 +0200)
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
Parts/Attachments: text/plain (27 lines)
>  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

For a future system te rules can probably be relaxed, but for 2e can't
you move the generating logic into the fdd file? The docstrip module
system has a a mechanism for evaluating booleans annd generating or not
generating lines in each file based on certain flags, I'd have thought
it would have been possible to extend that and end up with basic (even
if larger) fd files that are still automatically driven rather
than manually created. But I haven't looked at the exact tests you are
doing in the minion fd files though...


This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit: