Hi List:
Was wondering if any XML savvy folks out there might know how to track
down/correct a formatting error (?) in an XML file.
My brother is using some proprietary software to translate text in XML
documents into languages with diacritical characters. The output produced
by the software
Hi Scott
I'm no XML expert but tried your sample file with this XML Validator -
http://www.validome.org/xml/validate/
It complained about an HTML escape sequence aacute; As the XML file
is UTF-8 encoded it shouldn't be necessary to use HMTL escapes.
I've attached the actual error message.
Hi Scott,
Did your brother test what occurs in applying the rev command :
put uniEncode(fileURL,UTF8) into fileURL
to the text file before sending it to the proprietary software used to
output the XML file?
Best Regards,
P.
Le 12 oct. 09 à 09:19, Scott Rossi a écrit :
Hi List:
Was
Scott
I tried to open it with something (not Rev) that parses XML and get
the following error:
'The entity aacute was referenced, but not declared.'
Entities are different between html and xml, and XML only supports a
few as standard. Others have to be declared. (From my crusty memory. )
Recently, Pierre Sahores wrote:
Did your brother test what occurs in applying the rev command :
put uniEncode(fileURL,UTF8) into fileURL
to the text file before sending it to the proprietary software used to
output the XML file?
Hello Pierre:
I don't think the above will help -- as far
Recently, Peter W A Wood wrote:
I'm no XML expert but tried your sample file with this XML Validator -
http://www.validome.org/xml/validate/
It complained about an HTML escape sequence aacute; As the XML file
is UTF-8 encoded it shouldn't be necessary to use HMTL escapes.
Thanks for
Recently, Dave Cragg wrote:
I tried to open it with something (not Rev) that parses XML and get
the following error:
'The entity aacute was referenced, but not declared.'
Entities are different between html and xml, and XML only supports a
few as standard. Others have to be declared.
Hi Scott
On 12 Oct 2009, at 16:24, Scott Rossi wrote:
Thanks for looking Peter. It seems possible to discern the error
even just
using a Web browser, but how to correct it?
By changing all the HTML escapes to their UTF-8 Equivalent which is
will be a little laborious and beyond my
On 12 Oct 2009, at 09:30, Scott Rossi wrote:
(declare an entity = no clue).
That's because you are still sane.
No promises here, but if you insert the following at the top of the
document, just after the ?xml version=1.0 encoding=UTF-8
standalone=yes? part, it seems to display in
Sorry, my last posting contained some errors. (Copied from wrong file.)
I think this is correct:
!DOCTYPE document [
!ENTITY aacute #x00E1;
!ENTITY Aacute #x00C1;
!ENTITY acirc #x00E2;
!ENTITY Acirc #x00C2;
!ENTITY agrave #x00E0;
!ENTITY Agrave #x00C0;
!ENTITY aring #x00E5;
Hi Scott
Thanks for looking Peter. It seems possible to discern the error
even just
using a Web browser, but how to correct it?
By referring to a couple of tutorials and the dictionary, I managed to
cobble together this simple skeleton of how to correct the file using
RunRev. I'm sure
Inserting Dave's DOCTYPE declarations (2nd version) gets the file a
clean bill of health from xml nanny (http://www.versiontracker.com/
dyn/moreinfo/macosx/27761).
Best,
Mark Smith
___
use-revolution mailing list
use-revolution@lists.runrev.com
The others have answered the main question (with acute solution, you
might say...), but something that seems odd is that every single node
has a namespace. I've never seen that done before. Maybe the schema at http://schemas.openxmlformats.org/markup-compatibility/2006
is supposed to take
No promises here, but if you insert the following at the top of the
document, just after the ?xml version=1.0 encoding=UTF-8
standalone=yes? part, it seems to display in Firefox OK.
Adding the lookup table does indeed appear to make the XML display
properly. I've passed the info along to my
On 12 Oct 2009, at 14:38, Colin Holgate wrote:
The others have answered the main question (with acute solution, you
might say...), but something that seems odd is that every single
node has a namespace. I've never seen that done before. Maybe the
schema at
Dave-
Monday, October 12, 2009, 1:22:56 AM, you wrote:
Is this Microsoft's open xml format by the way?
Yep. That it is. The bloat is MS Word namespace tags on every element.
I'd be embarrassed to write something like
w:p w:rsidR=00E52FAC w:rsidRPr=002C0BD1 w:rsidRDefault=00E52FAC
Open XML? - oxymoron
MS has seemingly done the same thing for XML what they did for SQL, html and
javascript de-standardize it 'just enough' to make interchange more
difficult without their blessing.
-
Stephen Barncard
San Francisco
17 matches
Mail list logo
