Hi Sapphira and Lex, I am glad that Sapphira put her hands on. For the suggested split of Python 2 and Python 3 versions of asciidoc...
I knew I will not have too much time to do the port. Having also rather bad memory, I tried to be pragmatic to keep it together until it can be split. My opinion on Python 2 version is that if it was to be maintained for the future, it would require some rewrite. Maybe software experimental archaeologist can do it, but it is probably better to focus on Python 3 version only and to polish it nicely. My suggestion is to call the project asciidoc3, but the script should probably called (the plain) asciidoc. The reason is that some people may have toolchains set for the asciidoc and they may be more willing to switch without touching their scripts. Also, asciidoc can simply be asciidoc forever, without the need to express the version in its name. But it is the subject for a discussion. So, whenever the separation is necessary (in the sense the end user wants to use both occasionally), let the 3 is added. Otherwise, let make it simply asciidoc. Have a nice day, Petr -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
