public service announcement

[waider]

You might want to check that your client for this and other "weblogs" converts accented characters (such as é) to HTML entities. Because if it doesn't, then (a) you're violating spec and (b) you're counting on everyone reading your page in, one presumes, iso-latin-1 AKA iso-8859-1. Me, I browse in UTF-8, so I see question marks everywhere you've got an unconverted entity.

Comments

[ikkyu2.livejournal.com]

i emailed the phoenix (mac os 9 client) developer about it. he replied:

Phoenix does automatically transmute an é to "%E9" which is the Unix Ascii
code for an Acute E. Thats what the livejournal documentation suggests I do.

I have no clue if that helps at all.
~Chris

So sounds like your quarrel is with the livejournal dev team for recommending Unicode over entities, rather than with the individual client developers.

[waider.livejournal.com]

This would be the part in the protocol spec which says:

• Convert everything else to %hh where hh is the hex representation of the character's ASCII value.
  

Aside from noting that the above snippet in the docs doesn't close the <LI> tag, and is thus actually in violation of spec itself, the above is the encoding convention used for posting form data in such a way that it doesn't get mangled in the transfer. Which is fine; it means your non-standard character has the same numerical value on the server as it does on the client. It doesn't, however, alter the fact that it is wrong to put such characters in a HTML page. The documentation could perhaps be clearer on this point, I guess.