-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 BJörn Lindqvist wrote: > To me, that makes sense. An untranslated string is just as annoying as > a frequently segfaulting program. So lets treat the problems the same. > Code that changes behaviour shouldn't be committed unless the > documentation is updated. User visible strings shouldn't be changed > unless the translations are updated. Something like that?
I agree with the first part because updating the C locale documentation should be doable by any programmer capable of changing the behavior of the documented program. However, any programmer doesn't have the capability of updating all of the translations. I think that requiring translated strings before a check-in then becomes an onerous task. Adam Schreiber - -- Why isn't all of your email protected? http://gnupg.org http://enigmail.mozdev.org http://seahorse.sourceforge.net http://live.gnome.org/Seahorse -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFAjoqjU1oaHEI4wgRAu0CAJ9Bm7qPH9ASsHQKqIl+/BGp6jycYACg3Lx4 yY9XL5Ce+rIyZo+taIQvfRY= =3scE -----END PGP SIGNATURE----- _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
