Re: DOCBOOK-APPS: Customizing DocBook

"Sebastian Rahtz" <> writes:

>  writes:
>  > While there's no full implementation of DSSSL we'll have to hack the
>  > output or we'll never get what we want --- and _need_ --- to. 
> 
> I question the _need_, often. Standards can be changed.

:-)
Or adapted... Which is also a need for changing it if too many people
are doing this... :-)

>  > It's just a matter of
>  > _no_ choice to work in the correct manner. I hate that and it is very
>  > "expensive" and time consuming... 
> 
> I sympathize with your plight. My personal feeling is that standards
> will simply fall, and people will just accept the total dross they get
> from Microsoft products. 
> 
> When did you last drink coca-cola, eat a hamburger, or a pre-made
> pizza? were they the best food you could find?

Hmmm... The situation a _little_ different here. Although they were
not the best food I've eaten, they made their job: feeding me. 

DSSSL can't make a few things that are needed in many places (like
placing a line on the top of a page with "Chapter X - XYZ    page #"
above it). 

There are other minor things. I don't have all the knowledgement that
you do on DSSSL and ESIS to implement something more advanced using
it. But I do know some of the outputs that I'm using to hack on
them. I've disturbed you a lot with JadeTeX problems sometime ago (I
think you do remember that :-)). JadeTeX couldn't generate the kind of
output I needed. 

PLEASE: Note that when I write DSSSL above I'm talking about
Jade/OpenJade implementations of it. Below I'm talking about DSSSL
itself. 

The problem _IS NOT_ with JadeTeX, but it is with _DSSSL
implementations_. While they are not fully implemented, we won't be
able to make things the correct way. 

I don't think it's a matter of changing some standard, it's "just"
implementing it at it's full capacity. DSSSL is too complex,
unfortunately, and hasn't been fully implemented yet... 

-- 
Godoy.	<> 

Departamento de Publica踥es
Publishing Department                   Conectiva S.A.