Opened 9 years ago

Closed 8 years ago

Last modified 8 years ago

#188 closed defect (fixed)

UI-Language and Default Locale

Reported by: Batchheizer Owned by:
Priority: major Milestone: 1.3.3
Component: Lucide Core Version: 1.3
Keywords: Cc:

Description

Changing the default locale (System-Setup - Country Palette) does not change the UI-Language of Lucide. IMHO Lucide should detect at every startup the current locale and change the UI-language if possible. For example some WarpIN scripts (webDAV-Plugin, Amouse (?), SearchPlus?) do this via REXX. Maybe this is easy to implement.

Change History (3)

comment:1 Changed 9 years ago by diver

  • Milestone set to 1.3.3

comment:2 Changed 8 years ago by diver

  • Resolution set to fixed
  • Status changed from new to closed

(In [457]) possible fixed ticket:188

comment:3 Changed 8 years ago by diver

this is a chicken and egg situation here. we work only with the LANG envvar, which makes perfect sense to me. changing the default locale in the country palette doesn't set the LANG new. of course with some api's the new country palette can be read and also a new locale could be set. with DosQueryCtryInfo?() the new default country can be read. with UniMapCtryToLocale?() a locale to the country can be set. this probably works in a lot of situations. but not in all, as for _CH it gives me fr_CH. and this is not true for the whole country. so the LANG envvar way is the only one i see.

Note: See TracTickets for help on using tickets.