On 5 September 2012 00:41, Chris Jones <[email protected]> wrote: > On Sun, Sep 02, 2012 at 01:22:34PM EDT, Elena wrote: > >> according to the FAQ, non-breaking spaces must be entered as either >> entities or attributes. Are there technical reasons for this? One of >> the advantages of Asciidoc is that documents are readable, and having >> either an entity or an attribute instead of a non-breaking space >> character hampers readibility. Provided that the document uses >> a suitable encoding (i.e. utf-8), could non-breaking spaces be >> recognized as such and handled accordingly? > > Have you tried it? > > 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. >
Hi, 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. Cheers Lex > CJ > > -- > ALL YOUR BASE ARE BELONG TO US! > > -- > 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. > -- 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.
