On Tue, Sep 04, 2012 at 07:59:18PM EDT, Lex Trotman wrote: > On 5 September 2012 00:41, Chris Jones <[email protected]> wrote:
[..] > > I was not aware of this particular FAQ but I have never had any > > problems with literal U+000A non-break spaces in my documents.. at > > least with html and pdfs generated via a2x. > Yes, but it isn't guaranteed to work. The Unicode ability has > improved over the years, but IIUC asciidoc wasn't originally written > unicode aware and it doesn't use Python Unicode strings. In some > cases ordinary strings will successfully handle Unicode, but in some > cases it won't and thats why Python 3 changed such handling. Now you mention it, I remember having to fiddle something in python 2.4's ./encoding directory when I wrote a unicode-oriented utility a couple of years ago. I had completely forgotten about it and whatever I did was only briefly documented in whatever python module was involved... never bothered to write a patch or anything.. and since I have upgraded to python 2.6, I have no recollection of what I did at the time, and no way to find out.. The only thing I remember is that the problem concerned using non-ASCII literals in python scripts. Although the problem appears to be similar, I had never thought of this affecting asciidoc as well, especially since I do not remember having any issues with non-breaking spaces (or other non-ASCII stuff) in asciidoc documents. Perhaps these aspects were addressed or worked around with python 2.6..? In any case, thank you for your comment. CJ -- HOW ARE YOU GENTLEMEN? -- 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.
