It's been a long time since I've looked at this extension, but my best guess would be that a charcter in your dictionary is a unicode char that couldn't be serialized into XML, at least not by the code in my package. A unicode charcther could come from being copy/pasted from a text online or maybe from a Word document. Can you identify the charcther? It might not be visible in the plain text in the Umbraco dictionary?
If you cant identify the text and remove the charcther that's causing problems, I'd be happy to send you the source code to the package so you can add additional error handling or maybe expand the support for the charcthers you require?
Let me know if you are able to solve this on your own.
You're right. The character must have been copy/pasted and were invisible to editors. I was able to find the hexidecimal 0x03 character in the database:
select * from [dbo].[cmsLanguageText] where dbo.cmsLanguageText.[value] like '%' + CHAR(0x03) +'%'
After I removed the invalid character everything worked as intended!
I have seen similar problems when trying to publish a content node with a rich text editor containing certain chars like this one, so I thought it might be the same type of error.
Error when trying to export dictionary to XML
I get a error, when I try to export a dictionary to XML:
Server Error in '/' Application.
'', hexadecimal value 0x03, is an invalid character.
Umbraco 6.1.6
Dictionary Dashboard 0.9.3
Hi Christian
It's been a long time since I've looked at this extension, but my best guess would be that a charcter in your dictionary is a unicode char that couldn't be serialized into XML, at least not by the code in my package. A unicode charcther could come from being copy/pasted from a text online or maybe from a Word document. Can you identify the charcther? It might not be visible in the plain text in the Umbraco dictionary?
If you cant identify the text and remove the charcther that's causing problems, I'd be happy to send you the source code to the package so you can add additional error handling or maybe expand the support for the charcthers you require?
Let me know if you are able to solve this on your own.
Cheers
Dennis Milandt
Hi Dennis,
You're right. The character must have been copy/pasted and were invisible to editors. I was able to find the hexidecimal 0x03 character in the database:
After I removed the invalid character everything worked as intended!
Thank you very much
Christian
Excellent :-)
I have seen similar problems when trying to publish a content node with a rich text editor containing certain chars like this one, so I thought it might be the same type of error.
I'm glad you solved id.
Cheers
Dennis
is working on a reply...