Alan_Brown wrote:I would make the same argument for the next screen (the one where you fill in names) as well. In my opinion, the interface of MLS should be in a consistent language -- it makes little sense to me to change the language for a few screens. If the prompts for forms and certificates need to be in a different language, then all of MLS needs to be in that different language.
There are pros and cons for both ways. I like the "heads up" feature of having the language change, but if I then didn't know that language I would likely get lost in filling out the form. I think a better solution might be to populate the list in the base language, but then add the target language in parentheses afterward.
For example, if the base language was English you would see "
Officers Sustained -- Ward" as a form to select. If you then set the language to Spanish, then that option would repopulate as "
Officers Sustained -- Ward (Spanish)" or maybe even "
Sostenimiento de oficiales--Barrio de Estaca (Officers Sustained -- Ward)." This would provide a sort of "heads up" while at the same time letting you complete the form in English.
However, I disagree that MLS should be forced to stick to one language. Being able to switch to a different language on the fly can be useful in a variety of situations, one of which was discussed below.
http://tech.lds.org/forum/showthread.ph ... #post20284
I foresee that scenario becoming more and more common, even within the United States. In our stake we have a Spanish branch and a Marshallese branch. It would be so convenient for stake auditors to be able to switch MLS on the fly between English, Spanish, and Marshallese when supporting/training these units.