> Hello!
>
> At the end of February I have started to work from scratch on the new Czech
> translation, because the former one was far from complete. I based my
> translation on English files, but I was not sure in many cases so I also
> used Slovak and Spanish files a lot. Since I did the whole work from
> beginning I also decided to change the encoding. Why? Because IMHO UTF-8 is
> the future and everything else is the past. Czechs used ISO-8859-2 mainly on
> UNIX based systems and CP1250 on Windows systems. So we didn't have unified
> encoding anyway. I believe, that somebody who needs other encoding can
> convert those language files easily.
I'm not against switching charsets, but I see two major drawbacks:
1) It would require by the translator changing the charset to take care
of *all* existing phpgw_XX.lang files, so there's nothing left alone.
2) Make sure the new charset (usually utf-8) is common and not a problem
on the db side. This means that some db engines supported by egw could
require an extra tunning/tweaking to support utf-8. And what's worse,
existing installations could stop working successfully.
There's an extra issue that I don't know how it's built, and it's the
initial selection list that you can see in /setup when choosing the
charset for the language right before installing all apps.
Maybe in a future all translations will switch to utf-8, but I'd just
like to know any other reasons for a language not to switch (now or in
the future) to utf-8.
Regards.
- --
|----------------------------------------------------------------------|
| http://counter.li.org info: Linux user: 92390 - Linux machine: 39301 |
| Oscar Manuel Gómez Senovilla - omgsATescomposlinux.org |
| GPG Key at http://pgp.escomposlinux.org |
|----------------------------------------------------------------------|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
