I agree 100% with Dischi on this. Although i should understand english, dutch, german and french, i can't understand the rest. It's also a royal pain-in-the-ass to translate all those error messages because they contain "untranslatable" things like object and class names. And generally, translated error messages are completly incomprehensible for both user and developper.
Btw, i'am still translating to dutch, and i noticed that a lot of almost identical duplicate strings creeped in the i18n translations. Could we be a bit more carefull to avoid those? And for date formatting, can't we use a library that does this, with the right language and local "standard" formatting (like dd-mm-yy for eu, mm-dd-yy for us, etc) Mvg den_RDC On Monday 23 February 2004 20:25, Dirk Meyer wrote: > Gustavo Sverzut Barbieri wrote: > > We're not in string freeze yet, things may change before we came > > with pre-releases, but if you have some time to help now, send your > > work! > > About that: I vote against using i18n for messages we print with > 'print' or '_debug_'. First of all, we don't need it because the user > should never see this. Second and more important: I can't read a trace > in a language different from English and German and won't be able to > find a bug. > > > Dischi ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
