Hi Jean-Micehl,
* Jean-Michel POURE [EMAIL PROTECTED] [011028 18:23]:
psql uses your input literally - so is your console/xterm in
UNICODE/UTF8?
Client: \encoding returns 'UNICODE'.
Server: \list show databases. All databases are UNICODE (except
TEMPLATE0 and TEMPLATE1 which are ASCII of
* Bruce Momjian [EMAIL PROTECTED] [011011 22:49]:
Can I ask about the status of this?
I have sent a patch a few days ago solving the client-side issue (on
the pgsql-patches mailing list) for review. I think Tatsuo said it
looked OK, however he should confirm/infirm this.
There is still the
* Tatsuo Ishii [EMAIL PROTECTED] [011010 18:20]:
As said in another mail, I have tried to add iso-8859-15 (Latin 9)
iso-8859-16 (Latin 10) to PostgreSQL, I think I have done mostly all
that's necessary. But I miss two things :
ISO-8859-15 and 16! I don't know anything beyond
* Tatsuo Ishii [EMAIL PROTECTED] [011010 18:21]:
Receiving a request to add ISO 8859-15 and 16, I review the multibyte
support code and found several errors in it.
1) There is a confusion between LATIN5 and ISO 8859-5. LATIN5 is not
ISO 8859-5, but is actually ISO 8859-9. Should we
I've been looking a bit at the MULE encoding wrt to latin 9 and 10. It
seems that there is no support for the Euro at all in it.
e.g. when I tried to use recode, which does recognise iso-8859-15
and 16, and convert to MULE, whatever I do, I obtain EUR for the
euro sign, OE, oe, s, S, z, Z, Y
Hi,
As said in another mail, I have tried to add iso-8859-15 (Latin 9)
iso-8859-16 (Latin 10) to PostgreSQL, I think I have done mostly all
that's necessary. But I miss two things :
- latin92mic/mic2latin9/latin102mic/mic2latin10 in conv.c
- the leading character value in pg_wchar.h
I don't
Hi,
As said in another mail, I have tried to add iso-8859-15 (Latin 9)
iso-8859-16 (Latin 10) to PostgreSQL, I think I have done mostly all
that's necessary. But I miss two things :
- latin92mic/mic2latin9/latin102mic/mic2latin10 in conv.c
- the leading character value in pg_wchar.h
I don't
Hi,
I have been working a bit at a patch for that problem in psql. The
patch is far from being ready for inclusion or whatever, it's just for
comments...
By the way, someone can tell me how to generate nice patches showing
the difference between one's version and the cvs code that has been
Hi,
* Tatsuo Ishii [EMAIL PROTECTED] [010925 18:18]:
So, this shows two problems :
- length() on the server side doesn't handle correctly Unicode [I
have the same result with char_length()], and returns the number
of chars (as it is however advertised to do), rather the length
Hi all,
while working on a new project involving PostgreSQL and making some
tests, I have come up with the following output from psql :
lang | length | length | text| text
--+++---+---
isl | 7 | 6 | álíta | áleit
isl | 7 | 7 |
10 matches
Mail list logo
