Monday, 9 June 2008 12:05 PMI thought the new release would fix the problem where WLW encodes certain characters in the title into HTML entity tags. e.g. Pounds sterling symbol £ = £ - same with Euro symbol, same with a dash (hyphen) is converted into an n-dash.
Is that fix not in this release? It doesn't appear to be.
Which release will it be in?
Monday, 9 June 2008 10:12 PMHi RenesisX,
Which weblog are you publishing to (wordpress, blogger etc...)?
Tuesday, 10 June 2008 10:00 AMI'm using BlogEngine.Net.
Basically BlogEngine.Net stores the Title field as straight text and then HtmlEncodes it for viewing on the web.
I put a proxy in the way so I could see the traffic that WLW sends during Publish.
Now, when WLW sends the title it has already HTML encoded the entities such as £ and € symbol.
I don't want it to do this. I at least would like an option to send them as text rather than HTML :)
Thursday, 12 June 2008 9:45 AMBump :)
Thursday, 12 June 2008 11:31 PM
With BlogEngine 184.108.40.206, I am able to publish these characters as expected.
Which version of BlogEngine are you using?
- Edited by Pooja [MSFT] Thursday, 12 June 2008 11:33 PM More details
Friday, 13 June 2008 7:33 AMI'm also still seeing HTML entities in the title. The XML entities in the body are gone since the tech preview though. The problem for me is Swedish chars, which I need to manipulate using WP plugins upon posting to fix the slug problem that WP has with non-ascii chars. And if they're entities I can't manipulate them directly.
Using Wordpress 2.5.1, latest WLW in XHTML mode, but it seems this isn't related to WP or any other blogging software. Tried posting from another desktop client, w.bloggar, and it sent Swedish chars un-escaped without any hickups.
I would suggest some option to turn off entity conversion altogether, even in XHTML mode, for both title and body. At least for these obvious chars.
Saturday, 14 June 2008 2:55 AMModeratorbjorne, I think your problem is different than RenesisX. Your title is correctly escaped (though you would prefer that we not escape at all) while RenesisX is seeing over-escaping.
RenesisX, if this is happening in the latest versions of BlogEngine.NET you can fix it with a wlwmanifest.xml change. Let us know what version you're on.
Tuesday, 17 June 2008 9:42 AMHey Pooja & Joe,
I'm also using the latest version (220.127.116.11).
I think the biggest difference is that I'm using a MS SQL Server back end, not the usual XML data store.
I'm almost certain this is where the difference lies.
If there is a way to change the encoding behaviour via a manifest change, then I'd absolutely love to try it!
Can you tell me what lines to change?
Or supply a new manifest file?
Wednesday, 18 June 2008 12:13 AMModeratorRenesisX, if you already have a wlwmanifest.xml file and it already has an <options> element, add this inside your existing <options>:
Tuesday, 8 July 2008 2:10 PMJust wanted to say thank you for this reply. It solved our problem.
Is there a list of these extra options sub-elements?
Sunday, 13 July 2008 10:32 PMCheers! That did the trick. Swedish chars are now working. But I ended up using the registry trick that Joe suggested here instead because I share my wordpress files between several blogs (virtual multiblog).
And I got Transliterado to do character replacement now that the entities are out of the way. Brilliant!
Found a more complete list of manifest options here btw.