All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Introducing strings.xml is fine. However, we need a way to use different words per a panel on translation... English-only speakers sometimes are surprised to know the fact that "OK" on a button sometimes needs to be translated differently in panel-by-panel basis.
A feature such as "define a translation for OK once, then the translation replaces all occurences of the OK labels of all panels as adefault" is helpful. I'd say more than 90% of the "OK" buttons are fine with the standard translation. However, we definitly needs a way to specify some particular "OK" to be translated differently. For other words/phrases, the frequency of special translation may be larger.
Alissa Sabre added a comment - 09/May/08 08:07 AM I have a comment on the second item.
Introducing strings.xml is fine. However, we need a way to use different words per a panel on translation... English-only speakers sometimes are surprised to know the fact that "OK" on a button sometimes needs to be translated differently in panel-by-panel basis.
A feature such as "define a translation for OK once, then the translation replaces all occurences of the OK labels of all panels as adefault" is helpful. I'd say more than 90% of the "OK" buttons are fine with the standard translation. However, we definitly needs a way to specify some particular "OK" to be translated differently. For other words/phrases, the frequency of special translation may be larger.
Introducing strings.xml is fine. However, we need a way to use different words per a panel on translation... English-only speakers sometimes are surprised to know the fact that "OK" on a button sometimes needs to be translated differently in panel-by-panel basis.
A feature such as "define a translation for OK once, then the translation replaces all occurences of the OK labels of all panels as adefault" is helpful. I'd say more than 90% of the "OK" buttons are fine with the standard translation. However, we definitly needs a way to specify some particular "OK" to be translated differently. For other words/phrases, the frequency of special translation may be larger.