[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 michael ximian com 

--- shadow/60701	Tue Mar 25 08:48:34 2003
+++ shadow/60701.tmp.3522	Tue Mar 25 10:29:23 2003
@@ -182,6 +182,36 @@
 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 .
+
+------- Additional Comments From michael ximian com  2003-03-25 10:29 -------
+Sergey;
+
+If you can do a killall -9 bonobo-activation-server; a bonobo-slay,
+and log-in in a different locale, and repeat this localization problem
+- then there is indeed a bug; and I'm interested in it.
+
+Otherwise - there is nothing we can do. If there is a
+bonobo-activation-server left running between sessions - this is due
+to a badly behaved bonobo component, that has not quit cleanly. The
+component needs fixing - check to see what is still running after
+quitting a session.
+
+There is _NO_ way that we can make gettext produce different
+translations in different contexts. Consider that an applet /
+component may be rendering text to 10 completely different apps, each
+in different locales - it may then call a library method to get a
+translated string _How_ does that library method know which locale to
+return the string in ?
+
+That is one half of the problem; the other half is that applications
+except to get a handle to the same process irrespective of locale in
+many cases; otherwise we could simply spawn a new component per
+locale. Indeed - it would be nice to do this - but it requires server
+extensions etc. and the server is currently pretty unmaintainable /
+extensible. It's furthermore not clear that that is the right way to go.
+
+SO I think this is a combination of some badly behaved random
+component; and a rather more fundamental problem.




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