And so says Peter Amstutz on 06/09/05 11:41... > A related, larger issue is internationalization of VOS in general. I'm > not sure where to go with that, although Reed mentions one issue which > is including the text encoding in places like property datatypes and > talk messages.
In my professional experience, that's the root of too much evil :-) I'd just pick one and stick with it. (UTF-8, or UCS-32, or the other UTF thing out there). (On the Python wrappers, that would mean always returning unicode objects. Which is the way to go for python 3.0 anyway.) > We would also want to use gettext to support > translations for the UI of user apps like Ter'Angreal. Translating of client-server stuff (which will probably be in properties) is another, rather interesting topic :-) best, Lalo Martins -- So many of our dreams at first seem impossible, then they seem improbable, and then, when we summon the will, they soon become inevitable. -- http://www.exoweb.net/ mailto:[EMAIL PROTECTED] GNU: never give up freedom http://www.gnu.org/ _______________________________________________ vos-d mailing list email@example.com http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d