Re: [Gnumed-devel] config issues

[Hilmar Berger]

On Mon, 12 May 2003, Karsten Hilbert wrote:

> > 1. I18N gets the locale directly from some table in I18N.sql, but not from
> > the cfg_* tables, i.e. you can't set it using config parameters. Could we
> > change that behaviour so that config parameters are read at startup and
> > I18N tables are set accordingly ?
> The database "locale" is derived from the current system
> locale and set at startup. I'd like to see the rationale for
> doing that in another way. Please make a specific suggestion
> as to how to handle the locale. One way would be to set the db
> locale from the current system locale (with the sanity checks
> like we do now) except when set in the local config file in
> which case no cross-checks with the system locale are done
> (except that a translation is actually available) in which
> case one may end up with mixed languages: one from the DB, one
> from the frontend gettext. But one might argue that the user
> better know what she does when explicitely defining a DB
> locale in the local config file.
I always thought that we want only one common locale for DB and client. I
assumed you set the gnumed locale from the current system locale because
no other  information is available at the first run .
IMHO gettext and the DB should use the same locale, set by the user:

- if no config info is available, get the locale from system and set it as
a per-user option
- if config info is available, use this and ignore system locale
- if the user changes the gnumed locale, set the DB and gettext locale
either immediately or at the next start.

Hilmar