Tatsuo Ishii <ishii@postgresql.org> 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.

I'm confused. If this is exactly the same as EUC_JP, why do we need
any new code at all? Why not just a documentation addition saying
they are the same thing? Or maybe rename EUC_JP to reflect the new
standard number (we've certainly renamed encodings before).

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate

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 of JPUG has
same impression. Japanese po files are managed by JPUG and it would be
better to ask him or someone from JPUG who is responsible for Japanese
po files.
--
Tatsuo Ishii
SRA OSS, Inc. Japan

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

> 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 of JPUG has
same impression. Japanese po files are managed by JPUG and it would be
better to ask him or someone from JPUG who is responsible for Japanese
po files.
--
Tatsuo Ishii
SRA OSS, Inc. Japan

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate

Tatsuo Ishii <ishii@sraoss.co.jp> 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?).

That's certainly true, and it's not solved. But how does keeping the
Japanese po files out of the distribution improve the matter?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

> Tatsuo Ishii <ishii@sraoss.co.jp> 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?).
>
> That's certainly true, and it's not solved. But how does keeping the
> Japanese po files out of the distribution improve the matter?

Keeping out po files until the problem is solved is just my opinion.

If JPUG (or Japanese po files maintainers/volunteers) decide to
include them into PostgreSQL distribution, I have no right to prevent
it.
--
Tatsuo Ishii
SRA OSS, Inc. Japan

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Hi.

----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>


> Tatsuo Ishii <ishii@sraoss.co.jp> 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?).
>
> That's certainly true, and it's not solved. But how does keeping the
> Japanese po files out of the distribution improve the matter?

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. Then, The system of the support of Honda-san who was the
representative of the document team had functioned enough up to now.
However, it is not the one to refuse to do the distribution with the main body.
It should discuss it again in the document team for the reasons why the one
that was the effort to match to the release schedule of the main body becomes
stronger.

Anyway, Please wait for the response from Honda-san for a while.

Regards,
Hiroshi Saito


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

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 that the main
distribution has no Japanese support (I know because I get the confused
emails). I've an open offer from the Sun i18N people to help with this,
if they can coordinate with you.

--
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate

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
> surprised when they package PostgreSQL and find out that the main
> distribution has no Japanese support (I know because I get the confused
> emails). I've an open offer from the Sun i18N people to help with this,
> if they can coordinate with you.

Ahh yes, Certainly an offer from SUN of Japan.:-)
Then, The support was done as a volunteer with Honda-san. It seemed to be
wonderful that the spread of PostgreSQL promoted it by Solaris.!
The resource is being offered in the place where JPUG was open to the public.
I think that SUN of Japan obtained knowhow that takes there and evades the
problem. The support of the resource makes an effort to the utmost though we
are volunteers. Satisfactory results proves.!
Maybe, the problem is a release speed.... However, It might be the same even
if it puts it on official's place...

Regards,
Hiroshi Saito







---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

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 true, and it's not solved. But how does keeping the
>> Japanese po files out of the distribution improve the matter?
>
> Keeping out po files until the problem is solved is just my opinion.

Regrettably I am also the same opinion. It is the cause of an
unnecessary trouble to include japanese po file without a certain
betterment.

--
Hiroki Kataoka <kataoka@interwiz.jp>

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate