Re: [PATCH] Trackback+akismetcomments

On Sat, 29 Dec 2007, Michael Guntsche wrote:

> Well it fully supports non ASCII characters which escape does not do all to 
> well. As for supported in browsers all the current browsers support it, has 
> been tested with (IE 6,7, Safari, firefox and I think also an opera version).

sounds good.


> If utf-8 isn't used you almost always run into problems with international
> comments (Euro sign, japanese Names). You do not have that with UTF-8. AS
> you can see utf-8 is just used to get the comment to the server, later on it
> gets encoded to the blog encoding anyway.

oh, i definitely agree that UTF-8 is preferable. i just don't think we should 
have an encoding config variable, but hard-code UTF-8 in the comments plugin. 
if the comment gets to the server intact in UTF-8, and we then store and 
display it in a lesser encoding, we haven't gained much.

having said that, we could consider removing the config var in pyblosxom 2.0 
and making it UTF-8 throughout.


> Since we are talking plugins now. Do we have a defined way to deal with
> plugins and the different pyblosxom versions (1.4, 2.0-trunk). There are
> already changes in current trunk that break some plugins and more will
> follow. Should we have one plugin that works with both versions or two

i haven't considered the release process much. i've mostly been thinking about 
getting more tests in. feel free to throw something up on the wiki!

-Ryan

--
http://snarfed.org/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/