Subject: Re: [Boost-docs] Quickbook blocks for concepts
From: Daniel James (daniel_james_at_[hidden])
Date: 2010-02-10 18:23:43
On 10 February 2010 13:08, John Maddock <john_at_[hidden]> wrote:
> I simply don't see why that would be better - in fact I've had endless
> problems whenever a non-ascii character shows up in the XML
There are non-ascii characters in a few places in our documentation.
If something comes up, you should report a bug. If there are problems
with tools down the line then quickbook should escape the characters
> character escapes are fully supported by both XML and HTML
In the future quickbook might generate something other than SGML/XML
> and have the big advantage
> of displaying correctly in my text editor - or any text editor for that
> matter - unlike the UTF-8 !
That's why I said I'm going add support for a BOM. I'd hope that your
text editor would understand it. It's a bit embarrassing that
But if using UTF-8 is that difficult, it'd be better to implement a
native character escape. Escaped markup is opaque and I'm hoping to
get quickbook to be a bit smarter about unicode soon. We could use
something like '\u039e' or perhaps '[&39e]'.
This archive was generated by hypermail 2.1.7 : 2017-11-11 08:50:41 UTC