Re: [Gnumed-devel] problem bootstrapping 0.3

[Karsten Hilbert]

On Wed, Jul 30, 2008 at 12:41:44PM +0200, Gour wrote:

> I found out about that - my ../rc.d script calls initdb and I re-init db
> with UTF-8 locale and finally after bootstrapping from v2 --> v9 I got:
> 
> Done bootstrapping GNUmed database: We very likely succeeded. :-)

Well done :-)

> Karsten> However, the above is a special case: Gour's locale is C. 
> 
> Problem is that my locale isn't C, but Postgresql thinks it is :-)
Now, at the time of initdb the relevant locale *was indeed*
"C" - by whichever means.

> If I want to use hr_HR.UTF-8 for storing notes in Croatian, but still
> want to have English interface (that's what I do for the whole desktop),
> do I need to just initdb with hr_HR.UTF-8
Yes.

> and/or I need hr_HR version of GNUmed as well?
No. GNUmed itself (client and database) are utf8
back-to-back so you can store any character in any GNUmed
installation :-)   However, *sorting* when done by the
database will only be correct for the initdb locale.

So, now that your database cluster is reinitdb'ed to
hr_HR.UTF-8 it will both be able to host a utf8-encoded
database as well as properly sort Croatian.

Regarding the language of the GNUmed client - that's
independant of other things. As long as the shell you start
GNUmed in is set to English GNUmed will use English, too.

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