|
Monday 02 May 2005 7:36:00 pm
I wonder.... How would one test this breakdown? How would you break down the content to find the specific character which eZ publish is having qualms with? For Erik, I could see how you might try to submit smaller chunks of the content until you found the "block" of text which contains the "Invalid Unicode character sequence". For others trying to replicate the problem it becomes more complicated as I in the USA don't deal with Unicode very often and as such I'm not that familiar with it...I just don't know how that would work.. But even if I don't know I can see if I can't try to break down the error message. From the eZ debug information, It looks like Postgress(DB) is kicking the error. It kicks the error while performing the update query ... data_text='<?xml version="1.0" encoding="UTF-8"?>
<section xmlns:image="http://ez.no/namespaces/ezpublish3/image/"
xmlns:xhtml="http://ez.no/namespaces/ezpublish3/xhtml/"
xmlns:custom="http://ez.no/namespaces/ezpublish3/custom/">
<paragraph>Dette er ingressen. Den største skriftstykket kommer nedenfor. Ære være årelange forsøk på å utvikle den perfekte CMS-en.</paragraph>
</section>'
Now this is just a guess but is this a new problem with non-english content or a suddenly appearing problem with a brand new configuration. I don't know what I'm talking about but I would guess that PostgreSQL may benefit from configuration to support non-english characters or something along those lines ... It's not an answer but it's an idea, //kracker Can I kick it ? - A Tribe Called Quest
Member since: 2001.07.13 || http://ezpedia.se7enx.com/
|