>For example the german translations are encoded as iso-8859-1. >I'm not sure, but guess that this may cause some headaches when serving >content as utf-8. Or does the gettext library handle this some way?
gettext indeed handles that transparently. So there is no need to use only one encoding for a language. The encoding in the .po files is just for the .po-reader to know what to decode from, internally it's all unicode and it will be translated to the default encoding of django (usually utf-8). bye, Georg
