Language setting of browser and Application Primary Language

Question

Hi,
my browser is currently set to German, that's why the APEX builder is also displayed in German. Brrr, I like development environments when they are not displayed in English - sometimes you don't understand this translations :-)
But my problem now is that I have created an application and set the Application Primary Language to English (en).
I would now assume that all the text APEX is creating during wizard actions will be created in the Application Primary Language and not in the language the browser is currently set to. But all the text is created in the browser language!!!
I think that's not a good behavior, because if you have a multi user/multi country development, the developers have to change there browser settings so that we get a consistent application. But to archive that I have set the primary language for the application.
Patrick
Check out my APEX-blog: http://inside-apex.blogspot.com

Answer 1

Patrick,
The resulting "defaults" strings which are displayed/used in the wizards should be Estonian, because that's my primary language of the application. Does it really make sense to show them in English/German, ...? Because the result language of the application should be Estonian.A) And how exactly will the Builder obtain the Estonian translation of these strings or of the translation of these strings into any of the hundreds of other languages we know nothing about?
I think the answer is that the Builder should maintain an awareness of the language setting of the application being developed. During the generation of possibly translatable text, the wizards should use a translated message for that text/language if: a) the language is one of the ten languages in which we make the Builder application available, and b) the developer has installed that "language version" of the Builder application (even if they are running a different language version at the time of text generation). If either condition does not hold, then the text should be generated in the Builder's primary language (en-us).
The builder is no genius (or not yet ;-) ), so that's up to the developers when they are changing the primary language during development.B) I don't understand your point (what is up to the developers?). The point I was trying to make was that even if we concede that generated text from the Builder should ideally be in the language that is the current primary language setting of the application being developed, the Builder would not be able to make that accommodation during the execution of the portion of the Create Application wizard that creates pages (with generated text in some language) because this occurs beore the language selection is made. Of course, the answer is that the Create Application wizard should be changed to allow the language to be selected before any text can be generated. Wizards would then be able to generate text in the appropriate language according to the rules proposed in (A).
Why does the builder/wizard not use substitution strings (eg. #APPLY_CHANGES#, #NO_DATA_FOUND#) for this type of default text instead?This would result in "code" in areas of the metadata from which translation strings would be extracted into the XLIFF file. Translators would ignore this code so the ultimate translated application (and the primary) would need a repository in which to hold the desired text for each language to be supported and a method with which to dynamically lookup the translated text at runtime. I don't believe the current architecture supports this (apart from the fact that we don't currently do it this way) and I think the performance implications could be significant, but I could be mistaken on both points.
Wouldn't it help to translate the application too?I don't understand this suggestion.
Thanks for your input.
Scott