Closed Bug 303446 Opened 19 years ago Closed 19 years ago

commandline parameters for XULRunner localization story

Categories

(Toolkit Graveyard :: XULRunner, enhancement)

Product:
Toolkit Graveyard
Component:
XULRunner
Platform:
x86
All
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: andreas.otte, Unassigned)

Details

For running XULRunner applications with different locales as a minimum something
like the commandline parameters for this purpose used in firefox are needed: 

-UILocale <locale> 
(Start with <locale> resources as UI Locale)
-contentLocale <locale> 
(Start with <locale> resources as content)
The -UILocale flag should work already, and there is no such thing as a "content
locale" in toolkit apps (the language pack and the region pack are one and the
same).
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Okay, figured it out now. -UILocale <locale> is considered an application
parameter, not a XULRunner parameter, it has to come after the application
ini-file to work. I tried it before the ini-file and XULRunner just returned to
the prompt without doing anything.

-contentLocale <locale>  strangely is a parameter for toolkit applications. Take
a look at mozilla/toolkit/xre/nsAppRunner.cpp.

Thanks
No it's not ;-)

That's old documentation taken from the suite version of nsAppRunner.cpp, and
never cleaned up.
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.