NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
I agree (Score:2)
As far as XSLFO goes, the people I know who write books with it use PassiveTeX, not FOP, because FOP's output still sucks (i.e. doesn't use TeX formatting rules). However PassiveTeX is even harder to install, and you're still left in a maze of DTD's, catalogs, and TeX installation buglets. Gah!
I (strangely) have high hopes of these things getting better, particularly this year in the Perl arena where we've made some pretty massive advances in processing XML. I hope I'm not proved wrong.
Oh, and hfb - drop the trolling. XML is a good thing, and is here to stay. There's no equivalent of docbook out there in the "TeX" world. TeX is a publishing markup language, and docbook is a technical publication markup language. They are different things, period.
Reply to This
Re:I agree (Score:2)
I wasn't trolling actually...
Re: Splitting hairs (Score:1)
TeX is a publishing markup language, and docbook is a technical publication markup language.
The point is ASCII is easy to author in (at least I think so). Book printers need PS or PDF to print. Here, the source code (TeX or XML) is a convenience to the authors. The real world needs the information in a format usable by their tools. TeX isn't at all a general replacement for XML, but in the realm of publishing, it's often a better fit than docbook.
Let me be plain: I want XML and docbook to succeed. I do
Re: Splitting hairs (Score:2)
But yes, we agree.