On 9/05/2016 21:27, 'Ebbo' via Ukelele Users wrote:
> It didn't solve it for me. I'm still getting this very message.
>
> I'm using MBP 3,1 / 10.8.5 and used to use a previous version of U
> (2.1.5) and I think OS X, too, to create a custom layout five years
> ago (2011) that I still use and which I want to modify again. Updated
> to U3.0.3. Opening current input source creates "… not valid XML". Did
> a forum search, found this post, had a look into my .keyboard file,
> but it is in lower case. However, it is in 'xml 1.0' and in another
> post I stumbled across I noticed that the current version requires xml
> 1.1.
> Provided that *is* the problem, what needs to be done to convert the
> document to xml 1.1 (except from changing the declaration itself)?
I can't say for sure. XML parsing is a rather complicated thing, and I
don't understand the inner workings of the parser that I'm using, so
it's hard to diagnose. If you want to send the file to me, you can do
so. I'm pretty busy currently, but have some time available to look at
things like this.
The main change from XML 1.0 to 1.1 is to allow character references to
almost any Unicode data point. The only forbidden ones are the "not a
character" ones (U+FFEF and U+FEFF and also in other planes) and the
null character (U+0000). There are other changes in the definition of
what can be a name and so on, but they don't matter so much.
That said, the current parser is technically an XML 1.0 parser that I've
modified to handle the greater character range, so it's neither a 1.0 or
1.1 parser. I don't believe that the version number in the header is of
any relevance to the actual parser, but it does matter for other
programs that know how to handle XML (e.g. XML Spear).
John
--
John Brownie,
john_b...@sil.org or
j.br...@sil.org.pg
Summer Institute of Linguistics, Ukarumpa, Eastern Highlands Province,
Papua New Guinea
Mussau-Emira language, Mussau Island, New Ireland Province, Papua New Guinea