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

[Karsten Hilbert]

On Wed, Aug 10, 2011 at 04:16:57PM -0700, Jim Busser wrote:

> >> 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.
> 
> Thanks for helping clarify this. Can you enlighten as to what role would be 
> played by
> 
>       /en_CA/LC_MESSAGES/gnumed.mo
> 
> as to how that kind of pseudo-argument (?) is intended to be processed?

I am at a loss what you mean :-)

> … if UI translation depends on .mo files (none of which
> exist in my cloned git repo)

Indeed. .po files are "source" files while .mo files are
"binary" files. Repos best contain "source" files only.

> then -- in order for i18n to be
> supported running from git -- a user would need to have a
> suitable .mo already installed in a standard location

Either that or compile their local .po into a local .mo.

> (which is perhaps a scripted part of packaging releases)

Yes.

> e.g.
> 
> in my 0.9.9 client tarball I can find
> 
>       de-gnumed.mo
>       el-gnumed.mo
> 
> So if all of this correct, even if I made changes in a
> 
>       /Users/djb/git/gnumed/gnumed/gnumed/client/po
> 
> wouldn't
> 
>       ~/git/gnumed/gnumed/gnumed/client/po/create-gnumed_mo.sh
> 
> have to be manually called?

Yes. In fact: "create-gnumed_mo.sh en_CA".

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