[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Rounded beam bug

From: Han-Wen Nienhuys
Subject: Re: Rounded beam bug
Date: Tue, 19 Mar 2002 17:09:34 +0100

address@hidden writes:
> > > I am just still struggling with the new font setup.
> > > Mats is helping me and we are getting close!
> > 
> > Very good.  These changes will be folded in .44?
> No, the problem was in Rune's teTeX installation. The default
> paths in his libkpathsea.a didn't match the teTeX installation
> so the texmf.cnf file wasn't found, which means that nothing
> else was found either. The solution was to explicitly set
> What should be solved is the fontpaths make rule when you 
> have compile for multiple platforms, as you pointed out
> in a previous email. I'd really prefer if someone who knows
> more about these aspects of the building process could implement 
> that. 
> Also, what should be done is to clean up the environmental
> variable settings in ly2dvi. I'm working on that.

In my ly2dvi, I have 

        environment = {
                ## todo: prevent multiple addition.
                'TEXMF' : "{%s,%s}" % (datadir, kpse) ,
                'GS_FONTPATH' : datadir + '/afm:' + datadir + '/pfa',
                'GS_LIB' : datadir + '/ps',

what do you intend to fix exactly?

> I also 
> plan to try to get rid of these seperate files for each
> header field. It turns out it's actually fairly simple to 
> read the appropriate number of lines from the .tex file 
> for each field.

You may try, but I will reject that patch. I think that it is a
totally braindead idea to try to separate the completely arbitrary
user input (which is allowed in the header fields) and the equally
braindead and arbitrary TeX definition syntax with nested braces,
escape sequences and what-have-you. The separate file approach is much
more robust. You can still construct invalid (La)TeX, but it will not
confuse ly2dvi.


Han-Wen Nienhuys   |   address@hidden    | http://www.cs.uu.nl/~hanwen/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]