-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > For translation of non error message we have 2 possibilites (because no > error code is needed): > a) Use the same method as for the error codes and have a MSG_xxx key for > each message > b) Use inline messages (see also [1])). Doing so the inline messages are > used as keys if existing in the i18n-properties file. As translators > need to know which inlines can be used as keys the need to be put into > the default properties file (but commented) for having a list of > available keys > > What can be the preferable way? > >> My preference goes to the second solution as I believe it's the same process >> we're using for Studio. >> In Studio, we're also using the class name (where the message comes from) as >> prefix for the keys which makes it even easier to match strings in the >> properties file.
Using FQCN as prefix will make it impossible to avoid duplicated translations. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktdyKIACgkQ2lZVCB08qHF11wCgmSfvJV4KHbyXI8JKfPFfPDL6 4HQAn0ZqC8glRyY3p4baNX/NQiRJJRq/ =s/E6 -----END PGP SIGNATURE-----
