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

Guntsche Michael <mike-Z92qn3yYq0hWk0Htik3J/[email protected]>
Newsgroups gmane.comp.web.pyblosxom.devel
Message-ID <[email protected]>
On Mar 23, 2008, at 17:22, will wrote:
> So the big problem is that ...  I don't know whether I understand how
> people use PyBlosxom for non-english blogs.
>
> Do you write your blog entries in utf-8?
>
> Do you write blog entries in some other kind of unicode and expect
> PyBlosxom to do the right thing?
>
> What have you had to do to PyBlosxom 1.4.x to make sure it handles  
> your
> blog properly?
>
> Is there anything else I should know in order to build test cases to
> make sure everything is working correctly for PyBlosxom 2.0?
>

Sorry for the late reply.

Personally I write every entry in UTF-8. I although think that UTF-8  
should be the default encoding for pyblosxom 2.0. The only problem I  
see is that you never know how the entries are saved in the textfiles.  
So even if everything is set to UTF-8 in the config, a rogue text file  
may mess things up.
I thought about adding something like #encoding UTF-8, iso8859-1 to  
the text entries so you know what encoding they have. But I did not  
really like that idea in the end.

Kind regards,
Michael

-------------------------------------------------------------------------
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
smime.p7s (application/pkcs7-signature, 2.4 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.