Re: Lout backend

[Stephan V Bechtolsheim <svbechtolsheim@xxxxxxxxx>]

What is the advantage of having a lout backend compared to
other backends? Wouldn't it make sense to improve existing
backends instead of starting a new backend?

Just asking .....

StvB

--- Jean-Baptiste Nivoit <jean-baptiste.nivoit@xxxxxxxxxxxxxx> wrote:
> Hello everyone,
> 
>     i just wanted to say that i have a Lout back-end in the works for Jade,
> with
> an accompanying lout macro package, it already works satisfactorily on simple
> documents (the FreeBSD FAQ and some of the gnome documentation were rendered
> successfully enough to be readable, after having had the lout output
> processed
> into
> PostScript). I think i read somewhere that people were having trouble with
> how
> 
> to implement inherited characteristics in the Lout language: the solution i
> propose is
> to use a named (in lout parlance) parameter that defaults to the value of the
> named
> parameter of the same name in the englobing scope, for instance (for people
> familiar
> with the lout syntax):
> 
>     def @DummyFO
>         named @DummyIC {@DummyIC }
>     {
>         ...
>     }
> 
> Anyways, that code was written on a jade 1.2 tree, so i need to clean it up a
> bit and
> report it to the latest version before publishing a patch (BTW, anyone knows
> what the
> appriopriate way to submit patches for jade is?). The lout macro package
> (which
> basically declares a macro for each supported flow object class...) is far
> from complete,
> it barely scratches the surface of what needs to be done.
> 
> So if anyone is interested, tell me..
> 
>         jb (just thought some people might have an interest in this...).
> 
> 
> 
>  DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist
> 
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com


 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist