Re: Workplaces and Languages was Re: [Gnumed-devel] Release 0.5.rc3

[Karsten Hilbert]

On Wed, Aug 26, 2009 at 11:09:22PM -0700, Jim Busser wrote:

> >>rc4 does not appear to resolve the failure of any-doc language to be
> >>saved in the db... was it supposed to?
> >
> >Yes, but you also need the v11.rc4 database.
> >
> >It will/should solve the "language is not set properly".
> >
> >I haven't looked at "ignoring mismatch isn't properly
> >remembered" yet.
> 
> Once the 0.6.x branch would be started, can it further improve the
> language explanation?

Sure.

> 1) when the user is connecting to the database, what is actually
> represented in the offer to "set the language"?

It offers to set/adjust the language

- for the database account used (say, any-doc)
- for when strings are translated *in the database*

Example:

        select description from clin.encounter_type

will return untranslated encounter types. Whereas:

        select _(description) from clin.encounter_type

will return encounter types translated into the language the
user set for himself inside the database. The client can
still display any language it wants. This:

        print "Die Typen der Kontakte:"
        encounter_types = sql(select _(description) from clin.encounter_type)
        print encounter_types

will result in the German output "Die Typen der Kontakte"
and then the types of encounters in whatever language was
set in the database.

> Is the user setting
> it for their current session only, or for both current *and* future
> sessions for this one copy of the gnumed client?

For herself for this and future sessions.

> 2) when selecting GNUmed > Preferences > Database > Language, the
> user is presently informed
> 
>       " ... This setting will not affect the language the user interface
> is displayed in but rather that of the metadata returned..."
> 
> --> can this instead  offer
>       "This setting will not alter the language in which raw clinical
> data is stored, nor the detail of any data displayed,

Of course not, that ought to be expected. If that weren't
the case it would be a grave bug.

> but rather
> that of the "meta" data returned...

This will not explain why the user interface doesn't switch
languages (despite the setting being found under
"Database").

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346