One more bug to make Radio safe for incessant code posters: there's still a double-decode between the aggregator and the posting form, when you post from the News page. I've got it stopped, by changing a couple of lines in radio.macros.weblogPostForm, from:
initialtext = radio.string.decodeEntities (adrstory^.storytext + viatext)
bundle //link the globe to the HTML rendering of the channel
add (globe + " <i>Source: " + radio.string.decodeEntities (adrstory^.channeltitle) + "; " + adrstory^.time + ".</i><br><br>")
add (radio.string.decodeEntities (adrstory^.storytext) + "<br><br>")
to:
initialtext = adrstory^.storytext + viatext
bundle //link the globe to the HTML rendering of the channel
add (globe + " <i>Source: " + radio.string.decodeEntities (adrstory^.channeltitle) + "; " + adrstory^.time + ".</i><br><br>")
add (adrstory^.storytext + "<br><br>")
but I'm not yet sure if that has unfortunate consequences with something other than the stuff I've tested it on so far. It does seem to work fine with less than, greater than, and ampersands: encoded once in the original post, they go through displaying their characters, but go into a post from the aggregator still encoded (as they should be), and encoded twice in the original post they go through displaying what they would look like encoded once, but are still double encoded in a post from the aggregator, just like they should be. I haven't had much success with single encoded quotes or apostrophes, but I don't really feel much need to post them encoded, anyway, so if Radio wants to turn ' into an unencoded apostrophe, that's fine by me.
12:33:12 AM 
|
|
