<bug>: GNUmed > > database language problems

[Saša Janiška]

Report sent via GNUmed's handler for unexpected exceptions.

user comment : on setting client's GNUmed > > database language from en (??)
to the first of two en_CA listings offered to me, this bug was generated.

system account: jb
staff member : Dr.Leonard Horatio McCoy (LMcC = any-doc)
sender email : address@hidden

 affects gnumed
========================
Note this may be related to another language problem in which GNUmed recognizes a difference at login between the current database language and that on the user's machine however Setting to the user's machine language seems neither correctly handled nor remembered, see
http://lists.gnu.org/archive/html/gnumed-devel/2008-09/msg00505.html

[Jim Busser (jbusser)]

Set to "medium" on account of its capacity to annoy. Could be downgraded to "low" if the client at login defaulted to "ignore".

[Jim Busser (jbusser)]

 fixed in HEAD and 0.3.x
http://lists.gnu.org/archive/html/gnumed-bugs/2008-10/msg00004.html

[Jim Busser (jbusser)]

Client 0.4.6-1 still has problems. Even when (in GNUmed > Options > Database > Language) I would select en_CA and click OK and I am warned that the database currently holds no translations... and am asked "Do I want to force the language setting to [en_CA]?" and I click Yes, this is not remembered when I immediately re-select this menu item or when I would quit and re-launch GNUmed client.

Likewise at login to the database, even when one would (after the banner Welcome) be notified that no language is set and I would click "Set" in the dialog when asked if I want the database set to en_CA, it is not enacted (even after restarting the postgres cluster).