[gnome-cyr] [Bug 60701] Changed - activation does not pass LANG, other locale-related variables.



Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=60701

Changed by hvv hippo ru 

--- shadow/60701	Tue Mar 25 07:22:36 2003
+++ shadow/60701.tmp.8958	Tue Mar 25 08:48:34 2003
@@ -158,6 +158,30 @@
 WONTFIX? Don't you know that applets are not propertly localized - the
 applet I18N is BROKEN. Try to start gnome session with any non-english
 language and add any applet which is not shlib - you will see
 _English_ UI, not localized. For example, try multiload applet.
 
 The envs I got from /proc/{procid}/environ.
+
+------- Additional Comments From hvv hippo ru  2003-03-25 08:48 -------
+> The problem is that it's really not feasible to have a mixed language
+> desktop with out of process components - since gettext is
+> _fundamentally_ a single language per process translation tool.
+I'm sorry, but how gettext affects us here? It's OK to have different
+locales in different processes for gettext.
+
+As why one may need to run programs in different locales on the same
+desktop:
+1) a buggy program can just crash/misbehave if run in non-english locale or
+ behave differently.
+2) Translation may be too bad or very incomplete so poweruser may wish to
+work with app with e.g. english UI rather than semi-english-semi-something.
+3) User may have to work with files with names in different encoding
+than desktop's one - so user have to start the app with locale for
+the same language but different encoding.
+4) Translator may be wishing to check how app looks in english while
+translating to other language.
+5) Just for studying foreign languages people try to work with
+familiar apps with different language of UI.
+
+There are a lot of reasons, in fact..
+So it definitely shouldn't be WONTFIX .




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]