|
From: | Jim Busser |
Subject: | Re: [Gnumed-devel] Re: Possible solution for altering date formats (Debian)? |
Date: | Mon, 06 Jul 2009 17:07:15 -0700 |
On 2-Jul-09, at 2:04 AM, Karsten Hilbert wrote:
On Wed, Jul 01, 2009 at 07:19:52PM -0700, Jim Busser wrote:PG needs it to know how to sort data, among other things. It cannot change it either, even accepting changes in sorting, because that would invalidate indexes.Don't the indexes influence sorting?No, it's the other way round.Is it just the character set that is important to the consideration?No. The set itself doesn't have an inherent ordering.Alternatively in the GNUmed client menu GNUmed > Options > Database > Language there exist about five options none of which are en_DKThat is only about the language used to translate strings inside the database - nothing to do with the client user interface as such.Is the above selection only relevant to i18n .po files (if they wouldhave been supplied)?Not at all. Only to the language setting used inside the database. That is why it is grouped under "Database", after all.
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- 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) - whichever values had been provided, by the praxis, for things like encounter types, document types etc
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?
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? Also if the database language would later be unset, would users then be shown the System types instead of the local encounter types?
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)
2) Change the prompt to: "Encounter types can be renamed locally:" 3) Change the left column label to "Local name"4) Change the right column to a more suitable name than "System type" which is currently IMHO too technical. Maybe "GNUmed master type" ? 5) In the editing screen, change title bar to "Renaming encounter type locally:" 6) Make the labels (to the left of the fields) match the column names in (3) and (4)
[Prev in Thread] | Current Thread | [Next in Thread] |