Movable Type Community Forum > Polish characters error

Full Version: Polish characters error - XMLRPC

Movable Type Community Forum > Additional Resources > Tips and Tricks

jwiecki

Dec 23 2003, 11:27 AM

Hi!
How know? What's wrong?

I implemented MT on my serwer (asia.w.kom.pl) for my daughter and instaled blog clients (w.bloggar and Zempt) for easy posting for her.
When she posting and publishing on blog client without polish characters all it's ok.
When she publishing her post directly on web MT with polish characters - the same - it's OK.

When she writing post with blog client (both client) contain polish characters (like ążźńęłóć), she takes this error message:

"Error! Aplication failed during request deserialization: not-well format
(invalid token) at line 32, column 8, byte 438 at
/usr/lib/perl5/site_perl/5.6.0/i386-linux/XML/Parser.pm line 185"

I upgraded perl to version 5.8.2 and XML-rpc to version 2.30. Error don't hiden.
Please help me.
Thank's for all solutions

Jack Więcki

jwiecki@w.kom.pl

kadyellebee

Dec 24 2003, 02:38 AM

I'm not positive how w.bloggar handles this, but from this is from the Zempt support pages: Known Issues

QUOTE

"Error during request deserialization" messages
Your entry contains characters that the Movable Type server doesn't understand. These include curly quotes, copyright symbols, em dashes, accented characters, Asian characters, and other non-ASCII symbols. Remove these characters, change them to their HTML equivalents, or substitute other characters and you'll be able to post.

This is a limitation of Movable Type. We're working on a way to work around the limitation or help Six Apart remove this limit in the XML-RPC API.

Kristine

jwiecki

Dec 24 2003, 11:24 AM

OK
I resolved this problem myself. I upgraded perl to 5.8.0 version and XMLRPC to 2.31 version.
(The 5.8.2 perl version isn't suitable for 2.31 version of xmlrpc package). But I have other problem : the polish characters isn't right looking on MTblog :-(.
I must fight...

Thx
Jacek Więcki

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.