I had a similar problem too with latin á ú é í ó characters. Make sure the encoding of the xml file is UTF-8 and be careful if you convert it from ASCII.
I think that you have a quote char ( " ) somewhere inside a value in your XML file, for example: <Product productId="1ALCOIL3012" description="ALUM. COIL 54mmWx0.95"mmTH" productTypeId="FINISHED_GOOD" /> so the parser may think that mmTH is a field and you`re missing = before the next " Guido Amarilla 2006/11/7, Fabian Gorsler <[EMAIL PROTECTED]>:
Hi all, after I read your mails, I start to remeber. I had a problem which was quite equal... James Troup wrote: > There is something wrong in the way the date was parsed into an xml file > or there are some wrong characters. During my OFBiz project I expierenced some problems with XML im-/export, too. When exporting files, German umlauts were not represented in their correct XML entities (&#NNN;) and when importing them, the sax parser returned with an error because of malformed UTF-8 chars. This error occured if the content of the XML file was pasted into the Webtools form and if the file was accessed by OFBiz itself via Webtools. I could imagine the characters are not written using a XML printer, they are written to the XML file as they are in the database. I didn't investigate more on this topic, because there was no time for doing it. We just wanted to know, whether we could use the OFBiz-way of dumping the database or if we should backup the "traditional" way. Can anybody acknowledge this for current versions? If not, I'll check it on the weekend. If anyone wants to paste umlauts and test it: ä ö ü Ä Ö Ü (I hope no terminal will be broken after this mail. :)) HTH Best regards, Fabian.
--
