Hiroshi Saito wrote:
Hi.
From: Magnus Hagander [EMAIL PROTECTED]
But, Please see.
http://winpg.jp/~saito/pg83/pg83b1-err3.txt
Japanese_Japan.65001 is error...
Japanese_Japan is true.
Yes, that is expected. If you explicitly ask for the .65001 locale it
will try the one that doesn't
I did some test, but without success,
Pavel
I have win2003 Server .. with czech locales support.
I:\PGSQL\BINinitdb -D ../data -L i:\pgsql\share
The files belonging to this database system will be owned by user postgres.
This user must also own the server process.
The database cluster will
Pavel Stehule [EMAIL PROTECTED] writes:
could not determine encoding for locale Czech_Czech Republic.1250: codeset
is
CP1250
Hm, we seem to have missed an entry for PG_WIN1250. Fixed.
regards, tom lane
---(end of
[EMAIL PROTECTED] (Magnus Hagander) writes:
Re-allow UTF8 encodings on win32. Since UTF8 is converted to
UTF16 before being used, all (valid) locales will work for this.
So where do we stand on the Windows locale/encoding business --- are
we happy with the behavior now, or does it still need
Tom Lane wrote:
[EMAIL PROTECTED] (Magnus Hagander) writes:
Re-allow UTF8 encodings on win32. Since UTF8 is converted to
UTF16 before being used, all (valid) locales will work for this.
So where do we stand on the Windows locale/encoding business --- are
we happy with the behavior now, or
Hi.
Um, It seems that it only passed the strict check of chklocale.c. Probably, It may
enable mistaken selection...However, I will clarify a problem by the test.
Regards,
Hiroshi Saito
From: Magnus Hagander [EMAIL PROTECTED]
Tom Lane wrote:
[EMAIL PROTECTED] (Magnus Hagander) writes:
2007/10/16, Magnus Hagander [EMAIL PROTECTED]:
Tom Lane wrote:
[EMAIL PROTECTED] (Magnus Hagander) writes:
Re-allow UTF8 encodings on win32. Since UTF8 is converted to
UTF16 before being used, all (valid) locales will work for this.
So where do we stand on the Windows locale/encoding
Hi.
I can test it with czech locale. Can I download binaries anywhere?
http://winpg.jp/~saito/pg83/postgresql-8.3beta-cvs.tgz
It is a thing after regression test.(MinGW+gcc)
Regards,
Hiroshi Saito
---(end of broadcast)---
TIP 2: Don't 'kill -9'
Hi.
Um, It seems that it only passed the strict check of chklocale.c. Probably, It may
enable mistaken selection...However, I will clarify a problem by the test.
First, it is one problem
http://winpg.jp/~saito/pg83/pg83b1-err.txt
And a test continues
---(end
Hi.
Second, it is big problem
http://winpg.jp/~saito/pg83/pg83b1-err2.txt
It is text serch config error.
However, It passes initdb.(locale=Japanese_Japan.932 ... This is ShiftJIS
locale)
And a test continues
Regards,
Hiroshi Saito
---(end of
Hiroshi Saito wrote:
Hi.
Um, It seems that it only passed the strict check of chklocale.c.
Probably, It may enable mistaken selection...However, I will clarify a
problem by the test.
First, it is one problem
http://winpg.jp/~saito/pg83/pg83b1-err.txt
And a test continues
But
Hiroshi Saito wrote:
Hi.
Second, it is big problem
http://winpg.jp/~saito/pg83/pg83b1-err2.txt
It is text serch config error.
However, It passes initdb.(locale=Japanese_Japan.932 ... This is
ShiftJIS locale)
And a test continues
What text search config would you expect?
Hi.
Hiroshi Saito wrote:
Hi.
Second, it is big problem
http://winpg.jp/~saito/pg83/pg83b1-err2.txt
It is text serch config error.
However, It passes initdb.(locale=Japanese_Japan.932 ... This is
ShiftJIS locale)
And a test continues
What text search config would you expect?
This
Hiroshi Saito wrote:
Hi.
Second, it is big problem
http://winpg.jp/~saito/pg83/pg83b1-err2.txt
It is text serch config error.
However, It passes initdb.(locale=Japanese_Japan.932 ... This is
ShiftJIS locale)
And a test continues
The changes that were made were only to re-enable
From: Dave Page [EMAIL PROTECTED]
Hiroshi Saito wrote:
Hi.
Second, it is big problem
http://winpg.jp/~saito/pg83/pg83b1-err2.txt
It is text serch config error.
However, It passes initdb.(locale=Japanese_Japan.932 ... This is
ShiftJIS locale)
And a test continues
The changes that
Hiroshi Saito wrote:
From: Dave Page [EMAIL PROTECTED]
Hiroshi Saito wrote:
Hi.
Second, it is big problem
http://winpg.jp/~saito/pg83/pg83b1-err2.txt
It is text serch config error.
However, It passes initdb.(locale=Japanese_Japan.932 ... This is
ShiftJIS locale)
And a test
Dave Page wrote:
Hiroshi Saito wrote:
Hi.
Second, it is big problem
http://winpg.jp/~saito/pg83/pg83b1-err2.txt
It is text serch config error.
However, It passes initdb.(locale=Japanese_Japan.932 ... This is
ShiftJIS locale)
And a test continues
The changes that were made were
Dave Page wrote:
Hiroshi Saito wrote:
From: Dave Page [EMAIL PROTECTED]
Hiroshi Saito wrote:
Hi.
Second, it is big problem
http://winpg.jp/~saito/pg83/pg83b1-err2.txt
It is text serch config error.
However, It passes initdb.(locale=Japanese_Japan.932 ... This is
ShiftJIS locale)
Hi.
From: Dave Page [EMAIL PROTECTED]
Yes, Please see,
http://winpg.jp/~saito/pg83/pg83b1-err2.txt
Is that initdb is successful a problem as for this?
Oh, sorry - misread that. I chatted with Magnus about that. It is
correct, but misleading. pg_control will say Japanese_Japan.932 as well
Magnus Hagander wrote:
Not so. The locale is Japanese_Japan, really. That's the only part
that's relevant for UTF16 encodings, which is what we use to do UTF8. We
specifically *don't* try to use Japanese_Japan.65001.
Thats not what I mean. From a *usability* perspective, Hiroshi should
see
Hiroshi Saito wrote:
Hi.
From: Dave Page [EMAIL PROTECTED]
Yes, Please see,
http://winpg.jp/~saito/pg83/pg83b1-err2.txt
Is that initdb is successful a problem as for this?
Oh, sorry - misread that. I chatted with Magnus about that. It is
correct, but misleading. pg_control will say
But, Please see.
http://winpg.jp/~saito/pg83/pg83b1-err3.txt
Japanese_Japan.65001 is error...
Japanese_Japan is true.
However, The test of this state is continued.
But but but, Sorry, I face to a bed...
Regards,
Hiroshi Saito
---(end of
Dave Page wrote:
Magnus Hagander wrote:
Not so. The locale is Japanese_Japan, really. That's the only part
that's relevant for UTF16 encodings, which is what we use to do UTF8. We
specifically *don't* try to use Japanese_Japan.65001.
Thats not what I mean. From a *usability* perspective,
Hiroshi Saito wrote:
Hi.
From: Dave Page [EMAIL PROTECTED]
Yes, Please see,
http://winpg.jp/~saito/pg83/pg83b1-err2.txt
Is that initdb is successful a problem as for this?
Oh, sorry - misread that. I chatted with Magnus about that. It is
correct, but misleading. pg_control will say
Magnus Hagander wrote:
Dave Page wrote:
Magnus Hagander wrote:
Not so. The locale is Japanese_Japan, really. That's the only part
that's relevant for UTF16 encodings, which is what we use to do UTF8. We
specifically *don't* try to use Japanese_Japan.65001.
Thats not what I mean. From a
2007/10/16, Hiroshi Saito [EMAIL PROTECTED]:
Hi.
I can test it with czech locale. Can I download binaries anywhere?
http://winpg.jp/~saito/pg83/postgresql-8.3beta-cvs.tgz
It is a thing after regression test.(MinGW+gcc)
I have problem, there isn't libintl-2.dll
Pavel
Magnus Hagander [EMAIL PROTECTED] writes:
Dave Page wrote:
SJIS wasn't ever supported as a server encoding
(http://www.postgresql.org/docs/8.2/interactive/multibyte.html). The
fact that initdb continues if you use Japanese_Japan.932 is an
inconsistency I reported previously but has yet to be
Hi.
From: Pavel Stehule [EMAIL PROTECTED]
I can test it with czech locale. Can I download binaries anywhere?
http://winpg.jp/~saito/pg83/postgresql-8.3beta-cvs.tgz
It is a thing after regression test.(MinGW+gcc)
I have problem, there isn't libintl-2.dll
Ooops, sorry, it is full-build.
Hi.
From: Magnus Hagander [EMAIL PROTECTED]
But, Please see.
http://winpg.jp/~saito/pg83/pg83b1-err3.txt
Japanese_Japan.65001 is error...
Japanese_Japan is true.
Yes, that is expected. If you explicitly ask for the .65001 locale it
will try the one that doesn't have the proper NLS files, and
29 matches
Mail list logo
