On 26 March 2012 18:43, Gour <[email protected]> wrote: > On Mon, 26 Mar 2012 12:35:36 +1100 > Lex Trotman <[email protected]> wrote: > >> The answer may not be satisfactory, but it is the answer. Asciidoc is >> a small project and cannot expand its scope to include re-writing >> documentation of existing toolchains.
Note that Sphinx says nothing (that I could find, I might be wrong) about how to turn your Latex into PDF or anything else and refers to the rst2pdf docs or users writeups on how they set it up. > > I must say that I'm a bit surprised with the size of the project - it > seems that Stuart is practically the only one commiting the code > although I did believe that AsciiDoc is much bigger project. :-( Then if you like it add to it, if you think the documentation can be improved do it, or whatever help you can give. > >> Especially as any such time would detract from development of >> Asciidoc itself. > > How many people contribute code to it? Given that it is a mature tool, (version 8.6.7) Asciidoc is not evolving as rapidly as new tools like sphinx. So it is not surprising that Stuart does all fixes/adaptations from a number of sources. He is the main developer, like George Brandl is for Sphinx. > >> For example I don't give a damn about non-English languages, but I >> want better formatting of source code documentation (at the moment). >> What is important depends on the user. > > Sure, but from the tool using utf-8 by default one expects to have > decent support for non-English languages. Maybe I have misunderstood, what doesn't work? > > In any case, I'm thankful to you for this reply and I'm going to explore > quoting attributes/roles as well as re-consider reST/Sphinx considering > that, although I prefer AsciiDoc markup, the latter projects seems to > have much more people involved. Of course you should explore all avenues, but if you prefer one format then contribute to that project. A lot of the code changes in Sphinx seem to be done by George with others doing translations etc. But as I said above, Asciidoc is more mature and isn't going through the big evolutions that Sphinx is still having. Note that for PDF Sphinx generates either Latex, after which you need a Latex toolchain and its attendent customisation, or rst2pdf which seems to configure with a mixture of Python and Json. So you still have a learning curve there, although your latex experience might help you with that method. Cheers Lex -- You received this message because you are subscribed to the Google Groups "asciidoc" group. 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.
