-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cornelius Weiss escribió: > Hi Oscar, > > i like the idea of having only utf-8 as charset all over egw! I'm not a > charset expert, but afaik utf-8 covers all languages out there. i also > see the point of simplification. > Also the idea of incemental upgrading is fine for me. Maybe we can drop > all our historically updatescripts now in trunk. > > As for the phpgw -> egw transition in langfiles, i would say: just go ahad!
I've just done some commits in trunk for the phpgw_ -> egw_ change. I've tested locally before committing, and I think it works. Still testing and waiting for replies. Regards. > cu > conny > > Oscar Manuel Gómez Senovilla schrieb: >> Hi, all. >> >> >> This mail is just to get an idea about possible future plans (1.6? 2.0?) >> and/or just make suggestions. >> >> The main trigger of this is (at least) some issues about asking to >> switch some languages to utf-8. The *current* position is not to switch >> from an existing charset to utf-8, mainly because of some possible data >> corruption if upgrading from old versions (1.2 seems to handle data ok). >> >> Taking that some day these old versions will be totally unsupported >> (requiring if necessary incremental upgrades to at least 1.2 before the >> latest version), I think that at some time at the future egw will have >> to use utf-8 at least as main (even unique) encoding. At this time, >> non-utf8 installations that need some kind of syncronisation (at least >> icalsrv, but surely xmlrpc, too) need to do some extra setup to get any >> of these, because the standard says that data must be encoded in utf-8. >> Also, this would help to cleanup some code about charset conversion. >> About the issue of changing the encoding of language files not using >> utf-8, I would take care of it. About the data, I guess that should be >> done in tables_update.inc.php in phpgwapi. >> >> >> Another thing I think is in core dev's minds is to keep working on >> removing the phpgw prefix to be replaced with egw prefix in apps and >> dependencies. I did some test in the past about it and I didn't find it >> difficult for the code to use this prefix in the language files. >> >> >> I'd like to know this in order to give a more accurate reply to open >> tracker items willing to change now the charset, and to provide (if >> possible) some extra info beyond to just express what I'd like. >> >> >> 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 iD8DBQFHEkc9Qpr3kykd/aQRAuK1AJ9ZZdLR/CsSDGz2osNHDEIc9NXoLACfSPjI QzJ9AH/Ivx4U7sOS9y4d19c= =hnuh -----END PGP SIGNATURE----- ------------------------------------------------------------------------- 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-core mailing list eGroupWare-core@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/egroupware-core
