Re: [eGroupWare-translation] Japanese Charset?

[Moritoshi O. <m-o...@10...>]

Hi

At Fri, 30 Jun 2006 10:07:22 +0200,
Oscar Manuel =3D?UTF-8?Q?G=3DC3=3DB3mez=3D20Senovilla?=3D wrote:
>=20
> Moritoshi Oshiro (m-o...@10...) escribi=F3:
> >
> > Hi
> >
> > > Just a question to the Japanese translators....
> > >
> > > I am trying to use Japanese for my install, but all the translations
> > > are garbled...  (strange characters).
> > >
> > > My Database is MySQL 5 (latest as of this writing) using UTF8
> > > (utf8-unicode collation)
> > >
> > > I'm assuming the translations were done in another charset?
> > >
> > > If so, can someone provide me with a flat text file of the
> > > translations so I can put them into the UTF8 database?
> >
> > I had the same problem with egw 1.2, postgresql. The phpgw_ja.lang
> > files are written in EUC-JP which probably is the root cause of the
> > garbled(mojibake) chars.
> >
> > To display chars in UTF-8 correctly, you have to convert the files
> > from EUC-JP to UTF8 if it is a fresh installation.
> >
> > I do not know about how to change a charset if it was upgrading.
>=20
>=20
> I'm not a postgresql user/expert, but the theory for the charset conversi=
on
> for egw lang files is that the egw setup process "tweaks" the tables so t=
hat
> they use by default the specified charset. I don't know if at setup time =
this
> operation failed on the postgresql side or on egw side, so it would be go=
od to
> know. Also, it would be good to know if postgresql is capable of managing
> multiple charsets.
>=20
> With this in mind, one has to ask: is really EUC-JP the right charset to =
use
> for japanese? This decision corresponds to the japanese translators/users=
. At
> this time, you've both seem to have found that "utf-8 works better than
> euc-jp", and if this is true, maybe a change should be done. I don't mean=
 that
> EUC-JP is a wrong charset, but trying to cover all possibilities, maybe y=
ou
> have to think about switching to utf-8.
>=20

You must specify one encoding when creating db in postgresql. So, if
you need multi-lang, the solution is to use unicode. The first step is
to convert your data to utf8, then put it in your db, according to my
cool, technically reliable co-worker.

So, since egw did not convert euc-jp to utf8 during a fresh
installation, I changed ALL *_ja.lang files to utf8 first.=20

Sorry if I made confusions because of the info based on my poor
memory. I would really like to be accurate so let me reproduce later.
=20
=20
>=20
> > BTW if you are also translating the files, please let me know. I am
> > translating, and I do not like to work on something you are; I
> > think it is a waste of time.
>=20
>=20
> This is one of the purposes of this list. I expect news about if there are
> more japanese translators.

Yes, it would be really nice to know. I would like to join in an egw
user group in Japan if there is one. If there is not already, why not
make one so that we can work on translation, together?
=20
=20
 Do you have any info? > Oscar


Regards,=20
Moritoshi Oshiro