Bug#289144: acknowledged by developer (Bug#289144: fixed in afterstep 2.00.02-1)
On 22 Jan 2005 at 15:52, Bill Allombert wrote: Hi, Why did you set outputlanguage to C ? This effectively disables the translation! Yes, probably. I tought that setting outputencoding to ISO-8859-1 would break translations for non-Latin-1 languages (like Polish) but I hadn't tested it though. Menu methods should normally not change that setting (defined in /etc/menu-methods/menu.h) unless you use the translate() function manually. OK, I can remove the outputlanguage setting in the next upload of afterstep. Also I forgot to mention that afterstep should Conflics: with menu (=2.1.9-1) since woody menu does not support outputencoding. Acctually, afterstep depends on menu (= 2.1.14), so upgrading from woody shouldn't be a problem. Best Regards, robert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#289144: acknowledged by developer (Bug#289144: fixed in afterstep 2.00.02-1)
. * New upstream version: + correct behaviour of ClickToRaise option (closes: #288392). + problem with openning some applications shold be fixed too (closes: #286963). * menu-method: set outputencoding and outputlanguage (closes: #289144). Hello Roberto, Why did you set outputlanguage to C ? This effectively disables the translation! Menu methods should normally not change that setting (defined in /etc/menu-methods/menu.h) unless you use the translate() function manually. Also I forgot to mention that afterstep should Conflics: with menu (=2.1.9-1) since woody menu does not support outputencoding. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
