Re^2: XML parser error

Replies are listed 'Best First'.
Re^3: XML parser error by ikegami (Patriarch) on Jun 19, 2010 at 17:48 UTC
Switching to UTF-8 was to be done after and in addition to removing the `<?xml?>` directive from the included XML, if needed. You'll definitely get that warning as long as the `<?xml?>` line is in the included XML due to the bug. I was trying to foresee and fix problems you might have after removing the directive. You might have problems parsing an included file without its `<?xml?>` directive if it's not encoded using UTF-8. You might have problems including a file into a document that has a different encoding than the included file (but probably not). It's probably a good idea to use UTF-8 everywhere anyway, if you have a choice.	[reply] [d/l] [select]
Re^4: XML parser error by joeperl (Acolyte) on Jun 19, 2010 at 19:05 UTC
Hi, Correct if my understanding is wrong. You say that the UTF-8 can be used as below ? `<record xmlns:xi="http://www.w3.org/2001/XInclude" encoding="ISO-8859- +1"> <module type="record" name="module_a"> <data>data</data> <data>data</data> </module> </record>` [download]	[reply] [d/l]
Re^5: XML parser error by ikegami (Patriarch) on Jun 19, 2010 at 19:20 UTC
I have no idea what you are asking. Start by saying what problem you are trying to fix. But if that's really your XML's format and the encoding attribute specifies the encoding used, I can't help you. A scheme allows the encoding to change in the middle of the document is not only not valid, but so whacked out that I can't predict how it will behave.	[reply]