Re: [xmlroff] What needs to be done to make xmlroff a success?

[Tony G. <Ton...@Su...>]

Tony Graham <Ton...@Su...> writes:
...
>    What needs to be done to make xmlroff a success?

Taking some liberties with the posts from the last few days (and happily
listing contradictory ideas at this stage), this is the current list of ideas
for making xmlroff a success:

 - Implement...

 - Implement region-before, region-after, etc.

 - Implement markers

 - Provide RPMs as well as SRPMs and .tar.gz downloads

 - Provide a Windows port

 - Provide a Debian port

 - Provide a Solaris port

 - Improve developer documentation

 - Improve end-user documentation

 - Rewrite in a more OO language

 - Rewrite in...

 - Rewrite in D

 - Rewrite in C++

 - Keep it in C

 - Lose the reliance on GLib/GObject

 - Get rid of PangoXSL

 - Sack the maintainer

 - Put the statement of purpose on the xmlroff web page

 - Counteract outdated negative perceptions from when xmlroff used PDFlib

 - Be the best DocBook formatter on the planet

 - Support more graphics formats

 - Produce output in...

 - Produce output in SVG

 - Integrate with editors

 - Provide one-click formatting from within an editor

I'm just looking for ideas at this point.

 - What would it take for xmlroff to become the first thing you load onto your
   computer after the OS?

 - What would it take for you to junk your current word processor or
   formatting system in favour of XSL-FO and xmlroff?

 - What would it take for xmlroff to be your tool of choice for formatting
   XML?

Regards,


Tony.