Re: make web fails #2

[Han-Wen Nienhuys]

address@hidden writes:
> On Thu, 2004-08-19 at 07:44, Carl Sorensen wrote:
> > On Wed, 2004-08-18 at 16:28, Han-Wen Nienhuys wrote:
> > 
> > > Carl, can you select fonts by tacking any properties you need (and
> > > only those) onto the props variable passed via the markup system? It
> > > will make sure you select text fonts in the appropriate encoding. 
> > 
> > I'm not sure exactly how to do this. In my code I call fontify-text,
> > which needs a font as an argument. The code I use to select the font is
> > listed below:
> > 
> 
> After thinking about it more, it seems like perhaps the best way to do
> this is to replace fontify-text calls with interpret-markup calls
> 
> e.g. instead of 
> 
> (fontify-text my-font "abcde")
> 
> use
> 
> (interpret-markup paper (prepend-alist-chain 'font-family 'sans props)
> "abcde")
> 
> to return a stencil that I can then put in the proper location in the
> fret diagram.
> 
> Is this the right way to approach it?

That's better still, since then you're not tied to the specifics of
the text-output backend.


-- 

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