> The largest change in Python 3 is handling of strings. The amount of work > to port asciidoc using Python 2 to asciidoc3 using Python 3 must have been > significant. > > > Hi stargazer, yes in deed: the pitfalls of migrating Python2 to Python3 str/unicode was probably the most annoying and time-consuming challenge during my work (see asciidoc3.org or github.com/asciidoc3/asciidoc3). But in my opinion this leads to an advancement: now you can set different input-encoding and output-encoding, i.g. input file iso8859_6 (arabic), output mac_cyrillic (all right, just this makes poor sense) - and you can set errors, too, say 'ignore' ...
And to come back to 'I would hold off on that as there is currently an unresolved copyright / license dispute with this fork.' This is aimed at me: Think, we can find a solution asap, the solution is already initiated. Regards from Munich/Germany, Berthold -- 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 asciidoc+unsubscr...@googlegroups.com. To post to this group, send email to asciidoc@googlegroups.com. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
