[Catalog-sig] New PEP, pre-submission RFC
richardjones at optushome.com.au
Mon May 2 00:29:46 CEST 2005
-----BEGIN PGP SIGNED MESSAGE-----
On Fri, 29 Apr 2005 07:59 pm, Gerhard Haering wrote:
> For those who have names with characters not in ASCII, is that possible?
> do we just define that all text is UTF-8?
At the moment, the web interface / database is all UTF-8, so it therefore
assumes that submissions are UTF-8. I guess we should actually document
The one weak link of the current UTF-8-ness is the setup.py file, as you've
identified. In most cases that'll be the default encoding for Python code
(whatever that is, I should look it up ;) but in some cases it'll be
different. Regardless, we really need to UTF-8 encode the submission of the
setup.py-derived metadata to the webserver so there's no incorrect decoding
done at its end.
> Not that I really need it, but would this be the right time to think
> about optional description fields for other languages, too, like
> Description-fr, Description-de for French and German ones?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the Catalog-sig