severity 578797 wishlist tag 579797 +wontfix retitle 578797 DAViCal: UTF-8 capable PostgreSQL setup required for database creation thanks
On Thu, 2010-08-26 at 08:43 +0200, Frank Hartmann wrote:
> Hi,
>
> I found a workaround/solution:
>
> postgres stores some information at install time about the locale:
>
> postgresql.conf:lc_messages = 'en_US.UTF-8' # locale for
> sys
> postgresql.conf:lc_monetary = 'en_US.UTF-8' # locale for
> mon
> postgresql.conf:lc_numeric = 'en_US.UTF-8' # locale for
> num
> postgresql.conf:lc_time = 'en_US.UTF-8' # locale for
> tim
>
> previously that was set to de_DE which is apparently not working in
> combination with davical.
DAViCal creates the database with a UTF-8 encoding and PostgreSQL does
not allow UTF-8 encodings to be created if the database was originally
initialised with an incompatible encoding such as ISO-8859-15 etc.
There's not really any way around this. I don't believe that the
PostgreSQL folk will fix the issue - there are excellent performance
reasons behind their decision. CalDAV specifies UTF-8 as the One True
Encoding and so naturally DAViCal wants to store in a database that is
capable of that.
Possibly I could add a check during the installation, but it would say
little more than the PostgreSQL error message did, and it would most
likely say it in English, which would be a poor option indeed.
Regards,
Andrew.
--
------------------------------------------------------------------------
andrew (AT) morphoss (DOT) com +64(272)DEBIAN
You tread upon my patience.
-- William Shakespeare, "Henry IV"
------------------------------------------------------------------------
signature.asc
Description: This is a digitally signed message part
