Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
ISO-88591-1 problems and parse error -32700 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I have updated to WLW 14.0.5025.904, and now I cannot publish to my Wordpress install (2.6.2). WLW says parse error and the server code -32700. Beats me why. For various reasons I suspect the character coding, which is ISO-8859-1 in my Wordpress setting and set in WWLW blog settings (and also updated the blog configuration). On another blog I am using Movable Type 3.2, also with ISO-8859-1. I can publish to it, but the posts come out with national characters all messed up.
    In the previous version of WLW that I used, the body text came out fine, but the characters in blog title was messed up. Now on the MT blog the titles seems ok, but the body text is messed up.

    Anyone got any ideas? (except that I should switch to UTF-8, which I intend to do - but that is really difficult). Meanwhile, WLW is supposed ISO-8859-1.
    Tuesday, September 30, 2008 4:08 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi there, what WordPress plugins do you have installed? Also, if you View Source on your homepage and do a Find for "wordpress.net.in" does anything turn up?

    Do your username/password contain any national characters? If not, can you try a post containing only English and see if you still get the error?
    Wednesday, October 1, 2008 11:11 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks,
    I temporarily enabled a plugin so that you may see the ones I use, se http://www.weconverse.com/about/plugins/
    Nothing turns up on that in my home page.
    Nope, username and pw non-national chars.

    Tried posting:

    • English title and body - works fine
    • Swedish title and English body - gets publised, but the title is "umlauted" (i.e. looks nice but not searchable, became "Prövar ett inlägg"
    • English title and Swedish body - servlet error, parse -32700 etc.
    Anything else we can try?
    Please note that my MT blog (www.skolmarknad.info) is also messed up.
    In addition, I tried posting to one of my blogs hosted on Typepad (Swedish title and body). Was published, but again the title became umlauted but the body was OK.
    Thursday, October 2, 2008 11:31 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hmmm. Have you tried changing the charset in Writer? (Weblog | Edit Weblog Settings | Advanced) Can you try changing it to UTF-8 in Writer only, just to see what happens?
    Friday, October 3, 2008 6:21 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
     Swedish tite and body, post gets published. But title umlauted and body "Bortse frÃ¥n det här inlägget", i.e. the Swedish character "å" becomes "Ã¥"
    Friday, October 3, 2008 12:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    weconverse, please e-mail me at joe.cheng *AT* microsoft.com, with a pointer to this thread. Thanks.
    Thursday, October 9, 2008 5:02 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Joe, check.
    (mail is in da Net)
    Saturday, October 11, 2008 11:14 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    No resolution for this. WordPress (at least some installs) appears to choke on ISO-8859-1 data, only switching to UTF-8 fixes it (which requires that your blog be in UTF-8 format as well).
    Wednesday, October 29, 2008 5:18 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Joe, I hear you but do not believe that it is a Wordpress issue only. Mainly because strange things with ISO 8859-1 characters happen when I use WLW for a blog hosted by Movable Type as well. And that was not the case before WLW 14.0.5025.904. But who knows, guess I am on my own to solve this...
    • Edited by weconverse Monday, November 17, 2008 9:09 AM
    Monday, November 17, 2008 9:07 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi So we don't have a solution for this (?). 
    Friday, January 9, 2009 8:21 AM