Asked by:
WLW corrupting DBCS over XMLRPC

Question
-
I am trying to post Japanese and Chinese messages to my blog, but am unable to with Live Writer.
My main blog is using Ray Camden's BlogCFC with an MSSQL backend, and today I tested it against MangoBlog - another CF-based blog - with MySQL out the back.
Both had the same result - totally corrupted text. Both systems display Japanese fine when entering through their online administration forms, but of course I'd rather use WLW for all my posting.
The same post send to Windows Live Spaces displays fine.
Any idea what might be going wrong here?
Many thanks in advance,
-RobWednesday, December 3, 2008 4:19 AM
All replies
-
Are you familair with Fiddler?
http://www.fiddlertool.com/fiddler/
That tool will let you view all the commication between Windows Live Writer and you blogging server. I would use that first, and verify that Windows Live Writer is doing something wrong. But I have a feeling that your blog services just might not support these types of encoding through the XML-RPC endpoints.
-Brandon Turner [MSFT]Wednesday, December 3, 2008 6:00 PM -
Many thanks for the pointer, Brandon. Great to be able to see what is happening in real time, and - sure enough - Live Writer's output seems to be perfect.
I was a bit thrown by getting the same result from two different blogs, but it looks like they both share the same issue with Japanese/Chinese, and now I notice, English punctuation - quotes, dashes and apostrophes are converted into strange strings. Will take this up with the blog makers.
Many Thanks,
-RobThursday, December 4, 2008 12:04 AM -
What's the URL of your blog? What is View | Encoding (in your browser) set to when you view the blog, and does changing it to UTF-8 make our output look good (and everything else to look like gibberish)?
Thursday, December 4, 2008 2:11 AMModerator -
Hi Joe,
Thank you for following up.
My blogCFC is at http://web2.0japan.com/ ..
and Mango is at http://twitterlater.com/blog/ (although this seems to have some timeout errors occasionally.)
UTF-8 is selected in the browser's character encoding menu, so that seems ok.
I am pretty sure that the Japanese problem lies in the XMLRPC interface on the blog side, so I'm combing through the code to see if there is a missing charset declaration or something - but no luck so far.
However, a little googling shows evidence of other people having problems with punctuation and WLW on other services, etc. ... it seems these are called "Smart Quotes" !! :( So maybe there is something you can do with WLW to only send ... err ... "dumb quotes" :) .. like the ones that appear on this form
Regards,
-RobThursday, December 4, 2008 3:27 AM -
Ooops.... found the option to turn off smart quotes ... would be nice if they could be converted to decimal numeric character references - if that would allow them to round trip to the blog.Thursday, December 4, 2008 4:48 AM