Hi Lex, Am Mittwoch, 10. Oktober 2012 10:43:11 UTC+2 schrieb Lex Trotman: > > Hi Jens, > > You clearly do not understand open source software. Asciidoc was > developed by someone who had a need and was then made available for others > to use and contribute to. > Asciidoc is a translator to html and docbook. That is its purpose, not as > a document generation system with rendering capability. > It *is* already one ;)
> It is not in a "competition" with Rest or any of the other markups out > there, nor does it measure success by a head count. Nor does it need to > continually re-define its mission statement to capture new markets or to > derive a sustainable competitive advantage. It exists because it is useful > for its purpose, and that purpose continues to be needed by its developer > and contributors. > People decide between *AsciiDoc* and *ReStructuredText*. *AsciiDoc* is clearly the better markup language. Why not making this excellent product available and accessible for all? So you are suggesting that the project take on something clearly outside > its mission, which duplicates existing specialist projects (dblatex & fop) > and which significantly increases the workload on the project. > Not necessarily. The main missing use case for "common people" is asciidoc -> pdf and asciidoc -> odt. Unfortunately the first needs at least fop, but the chain asciidoc -> odt -> pdf would do also. I think this is even better, because beginners (as I am) never obtain exactly the layout they need, so they will have to touch the *asciidoc* output in *LibreOffice*anyway before printing or distributing. Concerning the workload, covering this main use case only needs to include the existing odf-backend code in the trunk distribution. The asciidoc->odtoutput enables "common people" to produce pdf from asciidoc without any big and complex infrastructure like *LaTeX*or *Docbook*. And, they still can adjust the final output via *LibreOffice*. My impression reading the past posts about the subject is, if you accepted the contribution of the odt backend author in your project, he would be pleased to maintain his code. The common user would not have to bother about incompatible plug-ins and could use *asciidoc* directly and easily. Besides, it would be really nice to have an editor with live preview like * ReText* especially for beginners. For the moment it renders only *markdown*and *ReStructuredText*. I do not think that adding support for AsciiDoc is a big thing if they agree. Still it needs time, seeing my workload for the moment it is not possible for me this year. Kind regards Jens -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To view this discussion on the web visit https://groups.google.com/d/msg/asciidoc/-/CTKc7lxGrhoJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.
