Tatsuo Ishii wrote:
Related to this, when are we going to get the Japanese po files in the
core distribution?
No idea. In my understanding, current message translating system has
serious problem if wrong locale and encoding is provided(has this
issue been solved in 8.3?).
That's certainly
Hiroshi,
We are doing the support including the trouble. It was thought that the
place of JPUG was preferable for the reasons why they were problems too
peculiar to Japan.
Well, some of PostgreSQL's commercial distributors have been pretty
surprised when they package PostgreSQL and find out
Hi Josh-san.
From: Josh Berkus josh@agliodbs.com
Hiroshi,
We are doing the support including the trouble. It was thought that the
place of JPUG was preferable for the reasons why they were problems too
peculiar to Japan.
Well, some of PostgreSQL's commercial distributors have been pretty
Tatsuo,
Related to this, when are we going to get the Japanese po files in the
core distribution?
--Josh
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Tatsuo,
Related to this, when are we going to get the Japanese po files in the
core distribution?
No idea. In my understanding, current message translating system has
serious problem if wrong locale and encoding is provided(has this
issue been solved in 8.3?). AFAIK Hiroki Kataoka, chairman
Tatsuo,
Related to this, when are we going to get the Japanese po files in the
core distribution?
No idea. In my understanding, current message translating system has
serious problem if wrong locale and encoding is provided(has this
issue been solved in 8.3?). AFAIK Hiroki Kataoka, chairman
Tatsuo Ishii [EMAIL PROTECTED] writes:
Related to this, when are we going to get the Japanese po files in the
core distribution?
No idea. In my understanding, current message translating system has
serious problem if wrong locale and encoding is provided(has this
issue been solved in 8.3?).
Tatsuo Ishii [EMAIL PROTECTED] writes:
Related to this, when are we going to get the Japanese po files in the
core distribution?
No idea. In my understanding, current message translating system has
serious problem if wrong locale and encoding is provided(has this
issue been solved in
Hi.
- Original Message -
From: Tom Lane [EMAIL PROTECTED]
Tatsuo Ishii [EMAIL PROTECTED] writes:
Related to this, when are we going to get the Japanese po files in the
core distribution?
No idea. In my understanding, current message translating system has
serious problem if
Tatsuo Ishii [EMAIL PROTECTED] writes:
I'm confused. If this is exactly the same as EUC_JP, why do we need
any new code at all?
I said *encoding schema is same, not the contents (character set) is
same. In another word, characters included in EUC_JP are not same as
Hi,
I would like to propose adding new character set JIS X
0213(http://en.wikipedia.org/wiki/JIS_X_0213).
JIS X 0213 is a relatively new Japanese goverment standard (defined in
2000, revised in 2004), and becomes important for Japanese
users. Moreover some commercial OSs including Windows VISTA
Tatsuo Ishii [EMAIL PROTECTED] writes:
I would like to propose adding new character set JIS X
0213(http://en.wikipedia.org/wiki/JIS_X_0213).
...
Note that since encoding schema of EUC_JIS_2004 is exactly identical
to EUC_JP, we can reuse existing encoding routines defined in
utls/mb/*.c.
Tatsuo Ishii [EMAIL PROTECTED] writes:
I would like to propose adding new character set JIS X
0213(http://en.wikipedia.org/wiki/JIS_X_0213).
...
Note that since encoding schema of EUC_JIS_2004 is exactly identical
to EUC_JP, we can reuse existing encoding routines defined in
Tatsuo Ishii [EMAIL PROTECTED] writes:
I would like to propose adding new character set JIS X
0213(http://en.wikipedia.org/wiki/JIS_X_0213).
...
Note that since encoding schema of EUC_JIS_2004 is exactly identical
to EUC_JP, we can reuse existing encoding routines defined in
Tatsuo Ishii [EMAIL PROTECTED] writes:
I'm confused. If this is exactly the same as EUC_JP, why do we need
any new code at all?
I said *encoding schema is same, not the contents (character set) is
same. In another word, characters included in EUC_JP are not same as
EUC_JIS_2004.
I'm still
Tatsuo Ishii [EMAIL PROTECTED] writes:
I'm confused. If this is exactly the same as EUC_JP, why do we need
any new code at all?
I said *encoding schema is same, not the contents (character set) is
same. In another word, characters included in EUC_JP are not same as
EUC_JIS_2004.
16 matches
Mail list logo