On Wed, Jul 08, 2009 at 09:43:17AM -0700, Jim Busser wrote:
>>> - optionally, the provision and configuration, at the machine-level,
>>> of a
>>> binary message catalog which provides a translation for all of the
>>> English program message strings (per wiki FrontendI8n)
>>
>> 1) this is necessary for successful translation, not optional
>> 2) GNUmed also supports local message catalogs, not only system-wide
>> ones
>
> the ability to fall back to the hardwired strings means that for the
> user (installed site) to bother to provide a binary catalog is optional
> (but necessary if they would desire a successful translation)
That is correct.
The hardwired strings are nothing but what's right inside
the code, btw. English (mine, mostly) is hardcoded into
GNUmed.
> do you mean that no matter which machine
> (and system account) this user would use, there is a per-gnumed-user
> language preference recorded in the database?
yep
This, BTW, enables the following scenario:
You are running GNUmed locally on your computer, in English,
on your local database.
Rogerio connects from his machine to your database and has
his frontend in Portuguese.
I run my client remotely on your computer (while the display
is on mine), in German, connecting to your database.
We all look at the same patient. While you see the encounter
type "in surgery" I see "in der Sprechstunde", while Rogerio
sees "in consultario" (or, rather, proper Portuguese ;-)