[cl-l10n-devel] i18n/normalize-locale-list question
Sasha Kovar
sasha-lisp at arcocene.org
Fri Aug 22 21:16:36 UTC 2008
Hi all,
I'm in the arguably unfortunate situation of living in en_US. Defining
resources in 'en' places them in en_GB (no complaints there). My default
*locale*, as loaded by get-default-locale, is the single en_US locale,
preventing lookup-resource from finding them.
Using the result of normalize-locale-list as *locale* fixes this, of course.
Is it more appropriate to e.g.
(let ((*locale* (normalize-locale-list (ensure-list *locale*))))
(lookup-resource "hi-there" nil))
everywhere i need to use *locale*, or would it make more sense for
get-default-locale to be calling normalize-locale-list internally?
Thanks,
Sasha
More information about the cl-l10n-devel
mailing list