Hans Dockter wrote:
On Oct 27, 2008, at 10:36 PM, Adam Murdoch wrote:
Having docbook integration might also be an interesting option for
report/website generation too.
I don't feel pain with the current way we generate the website. But if
it grows more complex things might change.
I think it would be nice to use the same source language for the user
guide content and the web site content, so that we can reuse content
across them.
- Better looking output
The pdf that latex produces looks dated (and not in a funky retro
kind of way, just kind of tired and old). I think the docbook
generated output looks better.
One unique selling point of LaTeX is that it is a true type setting
system. It calculates the position for every letter it writes, based
on algorithms containing many of the rules of the typesetting craft.
FOP uses the same layout algorithms as latex. The difference is probably
more in implementation maturity.
You can publish a book with LaTeX.
Yeah, but we're not. The output just has to be good enough. And so far,
latex isn't giving us that.
This is the reason why most of the modern mark up languages have a
transform to LaTeX code. But there is a docbook to latex converter (as
well as latex to docbook converter).
I did try the latex -> docbook converter as I was curious as to whether
we could roundtrip the documentation source, so that if we switched to
docbook, we could easily bail back to latex. The converter (which
happens to be my old friend tex4ht) died on our source. The exact same
source it generates html from. I gave up. Perhaps I could try out the
docbook -> latex converter, so that we would know the effort needed to
switch back to latex.
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
