Dealing with AFM files in Defoma scripts

[Ludovic Courtès]

Hi,

(If there is a more appropriate list for Defoma-related questions,
please let me know.)

I tried to write a Defoma application script for Lout.  Files that need
to be generated for Lout require actual data from AFM files rather than
Defoma hints.  For instance, the real AFM `FontName' is needed, rather
than the `FontName' hint (these happen to differ in some cases, for
instance for some of the `linux-libertine' fonts).

Is there a way to achieve this with Defoma itself or should I resort to
using the `Font::AFM' module?  The latter would introduce a new
dependency, which I guess would be an issue.

Thanks,
Ludovic.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Intention to drop sparc32 support for Lenny

[Ludovic Courtès]

Hi,

Frans Pop <[EMAIL PROTECTED]> writes:

> The problem is, and that has been mentioned before, that *there is no 
> upstream maintainer* for sparc32. Unless some people step up and ensure 
> that upstream issues _are_ fixed in a timely manner, sparc32 is 
> effectively dead.

"Upstream" should really read "kernel", right?

> Kernel development moves too fast for that.

Or does it wander too fast?  ;-)

Thanks,
Ludovic.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]