Nate Lowrie wrote:
> On Thu, Aug 7, 2008 at 5:14 PM, Nate Lowrie <[EMAIL PROTECTED]> wrote:
>> Buddy of mine checked out trunk, set the .pth file, and got this error:
>>
>> File "<pyshell#0>", line 1, in <module>
>> import dabo
>> File "C:\projects\dabo2\dabo\_init_.py", line 129, in <module>
>> dLocalize.install("dabo")
>> File "C:\projects\dabo2\dabo\dLocalize.py", line 53, in install
>> setLanguage(_defaultLanguage, _defaultEncoding)
>> File "C:\projects\dabo2\dabo\dLocalize.py", line 73, in setLanguage
>> daboTranslation = gettext.translation("dabo", daboLocaleDir,
>> languages=lang, codeset=charset)
>> File "C:\Python25\lib\gettext.py", line 469, in translation
>> raise IOError(ENOENT, 'No translation file found for domain', domain)
>> IOError: [Errno 2] No translation file found for domain: 'dabo'
>
> Ok, some more info on this...He is running Vista and I am running XP.
> I was able to replicate his problem. The issue is that the locale is
> actually being set.
>
> So, when I had him run locale.getlocale() it was returning
> ('English_United States', '1252'). If I called
> locale.setlocale(locale.LC_ALL, ""), I would set to that setting as
> well. When import dabo happens, dabo can't identify the
> "English_United States" as an alias and thus we get the translation
> file error because dabo doesn't know to map "English_United States" to
> "en". Paul, how do you want to fix this?
I believe dabo's locale module has a way to take an alias (of which the
aliases are platform-specific) and get the 'en' code from that. We
should try to hook into that, if so. Otherwise, we are going to be
adding these aliases manually and never getting them all.
Paul
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/%(messageid)s
