Hi Thomas,
on a second look I notice that your LC_* variables are missing the
encoding part. E.g. I have
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE=en_US.UTF-8
etc.
That assumes that locale is present on your system. E.g. on my Debian,
I would run
sudo dpkg-reconfigure locales
An alternative
Hi,
I'm a little confused about UTF-8/UNICODE locale settings for DSpace
using PostgreSQL v. 9.2.1.
By default, my systems are:
LANG=en_US
LC_CTYPE=en_US
LC_NUMERIC=en_US
LC_TIME=en_US
LC_COLLATE=C
LC_MONETARY=en_US
LC_MESSAGES=en_US
LC_PAPER=en_US
Hi Thomas,
there's very little reason to be concerned. The most important part to
get right is encoding when creating the database:
createdb -U dspace -E UNICODE dspace
What you mentioned is default locale set in shell environment
variables. DSpace (an Java in general) doesn't care about those
That makes a lot of sense, thanks!
A riddle, wrapped in a mystery, inside an enigma but that's my story and I'm
stickin' to it.
On 07/23/2013 10:23 AM, helix84 wrote:
Hi Thomas,
there's very little reason to be concerned. The most important part to
get right is encoding when creating the
4 matches
Mail list logo