Re: pyblosxom 2.0 and utf-8 -- help needed

<quote who="will" date="Sun, Mar 23, 2008 at 12:22:06PM -0400">
> Do you write your blog entries in utf-8?

Yep.

> Do you write blog entries in some other kind of unicode and expect 
> PyBlosxom to do the right thing?

Nope.

> What have you had to do to PyBlosxom 1.4.x to make sure it handles your 
> blog properly?

I don't remember having to do very much. What I do is assume a UTF-8
world. Everything (data, templates, webserver configuration) assumes
UTF-8. Doing anything else causes problems. I had to tweak a few things,
I think, to get UTF-8 comments but I believe it was on the webserver
side, not in PyBlosxom.

> Is there anything else I should know in order to build test cases to 
> make sure everything is working correctly for PyBlosxom 2.0?

There are a few places I'd be worried and careful to check that include:

  - configuration files
  - file names
  - tags, categories, metatdata, etc.

The other posters are correct that supporting other-encoding is going
to require additional metadata. That *may* be worth it for templates
and data files but for everything else, it might make sense
to say that it's UTF-8 or nothing.

> (As a side note, can anyone help me write those test cases?)

Sure. I can take a look.

Regards,
Mako


-- 
Benjamin Mako Hill
[email protected]
http://mako.cc/

Creativity can be a social contribution, but only in so far
as society is free to use the results. --GNU Manifesto

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

_______________________________________________
Pyblosxom-devel mailing list
Pyblosxom-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (GNU/Linux)

iD8DBQFH7sSLic1LIWB1WeYRAp6tAKDsRQWjXA721QQj4apg3vq1aKx2RwCgzbEJ
Yvka9aapz/MQUvRl3WbQ3xs=
=bJ8J
-----END PGP SIGNATURE-----