Difference between revisions of "Talk:EiffelStudio Internationalization"
| Line 24: | Line 24: | ||
'''--[[User:Patrickr|Patrickr]] 17:13, 13 November 2006 (CET)''' | '''--[[User:Patrickr|Patrickr]] 17:13, 13 November 2006 (CET)''' | ||
| + | |||
On Unix there are rules where which part of an application belongs to. Standardising this locations makes various things easier. | On Unix there are rules where which part of an application belongs to. Standardising this locations makes various things easier. | ||
Revision as of 07:13, 13 November 2006
--Patrickr 17:31, 9 November 2006 (CET)
The location for the mo files should be setup in the environment library, on Unix those files go under
/usr/share/locale
e.g.
/usr/share/locale/en/LC_MESSAGES/eiffelstudio.mo /usr/share/locale/de/LC_MESSAGES/eiffelstudio.mo /usr/share/locale/de_CH/LC_MESSAGES/eiffelstudio.mo
--Juliant 19:53, 10 November 2006 (CET)
Is it really necessary that the language can be changed while running EiffelStudio? I would say this is set once (even during installation). It wouldn't be a problem to just restart EiffelStudio.
--Ted 03:20, 13 November 2006 (CET)
What are the advantages of putting mo files under /usr/share/locale? mo files are not shared between applications and normally users do not need to change mo files. All mo files are put in ES installation directory, we only need to store the locale id as a preference. More over, mo files are implemented to be accepted by the library only with names of locale id.
We need to decide whether the language can be switched at runtime. Of course, not doing this as most applications definitely reduces a lot of time.
--Patrickr 17:13, 13 November 2006 (CET)
On Unix there are rules where which part of an application belongs to. Standardising this locations makes various things easier.
