gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Translatable database strings from within the client
Date: Wed, 10 Aug 2011 23:34:06 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Wed, Aug 10, 2011 at 02:28:20PM -0700, Jim Busser wrote:

> 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 ? 

No.

> 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 !]

Well, it says it right there.

Sure, this is a bit misleading since the "translation" is
linguistically correct. If you alter the translation (in any
way) it will likely start working.

Karsten
-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346



reply via email to

[Prev in Thread] Current Thread [Next in Thread]