> I just received an UTF-8 compatibility patch and japanese message file for
> PyCS from Yasushi Iwata. I am currently discussing it with him, but from a
> first look I would say it's a quite clean patch and we can pull it in. If
> somebody want's to look at it before it goes into CVS, I just attached it.
> After some questions are answered (for example I am currently not quite
> sure wether there would be a conversion step needed for existing data) I
> think I will integrate the attached patch into CVS.
We might want to think about what DefaultEncoding means -- the original
point of the config var was for the xml rewriting (Radio compatibility)
hack, but now it's being used to generate charset attributes on html / xml.
Do we want that? It might make sense to separate the two -- assume one
encoding, but always generate UTF-8, perhaps?
> Phil: looks like you need to put another contributor on your PyCS pages
> ;-) (and it would be great if you could skim the patch, too).
>
> Oh, Yasushi Iwata will send a PyDS patch for UTF-8 support, too, so after
> integration of these we will have a fully UTF-8 capable blogging solution!
That is _very_ cool :-)
Cheers,
Phil
Hi!
I just received an UTF-8 compatibility patch and japanese message file for
PyCS from Yasushi Iwata. I am currently discussing it with him, but from a
first look I would say it's a quite clean patch and we can pull it in. If
somebody want's to look at it before it goes into CVS, I just attached it.
After some questions are answered (for example I am currently not quite
sure wether there would be a conversion step needed for existing data) I
think I will integrate the attached patch into CVS.
Phil: looks like you need to put another contributor on your PyCS pages
;-) (and it would be great if you could skim the patch, too).
Oh, Yasushi Iwata will send a PyDS patch for UTF-8 support, too, so after
integration of these we will have a fully UTF-8 capable blogging solution!
bye, Georg