Print

Print


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

David

________________________________________________________________________
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:
http://www.star.net.uk
________________________________________________________________________