Re: [Gnumed-devel] Re: Possible solution for altering date formats (Debian)?

[Karsten Hilbert]

On Mon, Jul 06, 2009 at 05:07:15PM -0700, Jim Busser wrote:

> Apologies for my ongoing slowness here. The client user interface is  
> controlled, among other things, by:
> - the machine's (or overriding user-level) LANG and LC_ settings

This defines which language a message catalog file is
searched for before falling back to the hardwired strings
(often English).

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

> - whichever values had been provided, by the praxis, for things like  
> encounter types, document types etc

That is right.

> There is also in the wiki "BackendI18N" which includes "How to provide a 
> translated column", "How to add a translation target (language) to the 
> database" and to "allow user to select a default output language".
>
> So it is seeming to me that the selecting / setting of a database  
> language *does* (or has been intended to) affect what the user sees?

That is correct.

> When a user would alter the 'Encounter types" in order to provide a  
> "Local name", does the backend expect, and hope that these corresponded 
> to whatever language the backend had already been "set" to?

Since it cannot know (due to it not "speaking" the foreign
language) it must assume as much, yes.

"Set to" being "for that database=GNUmed user".

> Also if the 
> database language would later be unset, would users then be shown the 
> System types instead of the local encounter types?

That's right.


> PS in the "Editing encounter types" window, can we:
> 1) Change the window name to "Managing encounter types" (because it is 
> only in the deeper window that editing is done)

Done.

> 2) Change the prompt to: "Encounter types can be renamed locally:"

But types can also be added and deleted ?

> 3) Change the left column label to "Local name"

Done.

> 4) Change the right column to a more suitable name than "System type"  
> which is currently IMHO too technical. Maybe "GNUmed master type" ?

Done.

Could I have thought of one I'd have done it back then :-)

Oh, wait, what about not thinking of the "System name" as a
*name* but as an actual type. Hence it would become simply
"Encounter type" :-)     or even just "Type"

> 5) In the editing screen, change title bar to "Renaming encounter type 
> locally:"

-> "Editing local encounter name"

> 6) Make the labels (to the left of the fields) match the column names  in 
> (3) and (4)

Done.

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