On 3 September 2012 03:22, Elena <[email protected]> wrote: > Hello, > > 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?
Hi, Although the current asciidoc does its best with non-ascii characters, it is limited by Python 2, and should really be considered *ascii*doc as far as the input is concerned. Long term the Python 3 port will probably have better unicode support but there is no schedule for its release. Even then I am not sure that putting nbsp in the document is a good idea. It is not visually differentiable from the ascii space so particular rendering effects would be unexpected, someone editing may easily replace it with a space and break the output etc. In general despite the visual noise I would stick with an explicit marking of something with special semantics. You could of course choose your attribute or replacement (something you didn't mention) to minimise the visual effect. Cheers Lex > > Thanks. > > -- > 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.
