>
> Do you mean the Setting of charset while translating the phpgwapi?I
> have set the charset for the "Destination Language" in the
> Translation Tools in the the Section of phpapi,first of all.
>
> My translations work fine in the environment of egroupware(-in the
> egroupware site on my pc).
>
> My problem is when I open : \calendar\setup\phpgw_el.lang for all
> applications.-instead to see the translated phrases I only get ###
> and 3-digit numbers and ; .
I'm not sure to understand what you mean when you say "open" the file.
You don't "open" the file, I guess you mean "I choose to translate
calendar in translation tools, using 'el' as destination language", and
you see there the encoding problem. I suggest to go to /setup, and in
the check installation form, check possible warnings about mbstring.
If this is your problem, I guess it must be something related to your
installation, because in my installation I see "perfect strange" greek
symbols in translation tools. I've also logged in using choosing greek
as language, and it all looks greek symbols to me, including calendar
app. There's something wrong in the javascript calendar with non-ascii
characters, but this happens in spanish, too, so I don't think it's the
problem you describe.
> I want to do this in order to make some final spelling corrections
> with a spelling checker so as to be sure that there are indeed no
> mistakes.
>
>
> This encoded text for Greek language I want to see it normally-that
> is, not encoded with ## and so on.
>
>
> 1)The "destination Language" is Greek with the charset : "ISO-8859-7"
> and 2)at the Setup page it says that both English and Greek are
> curently installed and that the Current system-charset is
> 'iso-8859-1'.
The first is ok. The second means just the charset for apps, not ui, but
I think that also means that you installed first english alone and then
your language. Anyway, you can change the used charset by following this
article:
Regardless of your issue, and to remember to anyone who is not aware, I
exposed the core devs to fully switch all to utf-8 for egw 2.0 (or
possibly next stable release after 1.4, if any), whenever it is to be
released, together with renaming of lang files from phpgw_*.lang to
egw_*.lang, so many problems disappear. There wasn't a *full* *explicit*
"yes" but nothing against it, so I took it like a "yes, if we see it
works with no regressions". I've been (and still am) somehow busy, but
maybe I ask again and next weekend (in about ten days) I could dedicate
the necessary time to do at least the renaming for trunk.
I'm not sure if I contacted you for an account at my site, so please
mail me privately if I didn't, to give you the necessary details.
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
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________
eGroupWare-translation mailing list
eGroupWare-translation@... https://lists.sourceforge.net/lists/listinfo/egroupware-translation
