Re: [Gnumed-devel] Translatable database strings from within the client

[Jim Busser]

Also, I am noticing in my log the following… does

        ${GNUMED_DIR} not set

need resolution for i18n to work in en_CA / Mac OS ? 



locale.getdefaultlocale() - default (user) locale: ('en_CA', 'UTF8')

…

domain not specified, deriving from script name
text domain is [gnumed]
searching message catalog file for system locale [en_CA]
${LANGUAGE} = [None]
${LC_ALL} = [None]
${LC_MESSAGES} = [None]
${LANG} = [en_CA.UTF-8]
preferring local message catalog
looking above binary install directory [/Users/djb/git/gnumed/gnumed/gnumed/po]
looking in binary install directory 
[/Users/djb/git/gnumed/gnumed/gnumed/client/po]
system is POSIX, looking in standard locations (see Python Manual)
looking at ${GNUMED_DIR}
${GNUMED_DIR} not set
trying [/Users/djb/git/gnumed/gnumed/gnumed/po](/en_CA/LC_MESSAGES/gnumed.mo)
trying 
[/Users/djb/git/gnumed/gnumed/gnumed/client/po](/en_CA/LC_MESSAGES/gnumed.mo)
does not translate: [Translate this or i18n will not work properly !] => 
[Translate this or i18n will not work properly !]
trying 
[/opt/local/Library/Frameworks/Python.framework/Versions/2.6/share/locale](/en_CA/LC_MESSAGES/gnumed.mo)
falling back to NullTranslations() class



-- Jim