gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Re: Possible solution for altering date formats (Debi


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Re: Possible solution for altering date formats (Debian)?
Date: Wed, 1 Jul 2009 20:45:18 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

On Wed, Jul 01, 2009 at 11:07:34AM -0700, Jim Busser wrote:

> Interesting...
>
> ... despite that it was as root that I did dpkg-reconfigure and enabled 
> en_DK.utf8 as the only locale, and set it as the default,

It's like telling a child: Your only tongue shall be Amharic
henceforth ! -- if she never learned Amharic she ain't going
to speak it.

Do you have "locales-all" installed ?

> when I 
> restarted the computer:
>
> - the bootup echos issued a warning that Postgres had a problem because 
> the server could not be initiated with the locale en_CA.utf8 becuase it 
> did not exist but more interestingly
>
> - the system issued a dialog box advising me that because en_CA.utf8 did 
> not exist, the system default (C ?) would be used.
>
> I am not sure why that would be...

C isn't really a locale. It is the absence of any.

> maybe something about the locale that 
> was chosen during the installation needs to be kept available.
At least for the PostgreSQL server.

> The gnumed-client could then not connect to the backend... I was issued 
> (no surprise) a message that no server was accepting connections on that 
> socket.
>
> I again ran dpkg-reconfigure locales, included en_CA.utf8 (along with  
> en_DK.utf8) in the locales to be generated,
Which would be entirely unnecessary when installing
locales-all -- it simply generates all locales once.

> and despite that I did still 
> set en_DK.utf8 as the default, but which seems to be ignored, because 
> after rebooting when I ran
>
>       env
>
> I saw that while LC_TIME was en_DK.utf8 my LANG and GDM_LANG were both 
> still defaulting to en_CA.utf8

all the LC_* can be set independently

also, setting it for root doesn't force it for other users

> So within the current session, as normal user jbusser I did
>
>       LANG=en_DK.utf8
>       GDM_LANG=en_DK.utf8
>
> and then
>
>       &> LC_TIME=en_DK.utf8 ./gm-from-cvs.sh
>
> but it still made no difference in GNUmed.
Well, yeah, because en_DK.utf8 apparently displays dates the
same way as en_CA.utf8 (remember how I posted the screenshot
- which showed dates different from my de_DE but the same as
your en_CA ?)

> Maybe if postgres is installed as part of the debian installation,  
> something about the original locale becomes a postgres default that  
> requires that locale to remain available even after the system would  
> have its default altered.

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.

> Alternatively in the GNUmed client menu
>
>       GNUmed > Options > Database > Language
>
> there exist about five options none of which are en_DK

That is only about the language used to translate strings
inside the database - nothing to do with the client user
interface as such.

> and the widget  
> seems not fully enough yet developed to permit to create New or Edit or 
> Delete.

There isn't any new/edit/delete with that - managing locales
is an admin affair. Only choosing among the available ones is
of the user's duties.

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]