[eGroupWare-translation] [eGroupWare-developers] Proposal for changing the lang files directory

[Oscar Manuel Gómez Senovilla]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all.


About the proposal I wrote some time ago (quoted below) I've received
Ralf's permission to go ahead with it. So, in a few moments, I'll commit
a patch (the proposal is for trunk only) whose first effects are:
1) Hopefully, everywhere a lang file is needed to be loaded, the paths
for searching the lang files will be <app>/lang/egw_*.lang (new),
<app>/setup/egw_*.lang (still current) and <app>/setup/phpgw_*.lang (old
for backwards compatibility), in this order, winning only the first one
found.
2) Will NOT automatically create the new (<app>/lang/) dir. After the
patch, during this weekend, I should be able to migrate all the apps in
trunk from setup/egw*.lang to lang/egw_*.lang. So, if if between the
commit of the patch and the migration of an app a translator uses the
developer_tools in order to do a translation, this will (try to) go
directly into <app>/lang/egw_XX.lang, so in this case he should create
the lang dir himself and provide write permissions for the webserver.

I'm not 100% sure, but at least because of translation, you can remove
the write permissions for every <app>/setup directory. I'll try to add
in check_setup something about this.

I hope everyone is happy with this change.


Regards.

I'd like to know your opinion about I've been thinking about for a lot
of time, but never had the time to do it.
As surely (at least) most of you know, egw has always placed the
translation files (egw_*.lang) in a directory called <app>/setup/,
except for the "setup" application itself, being in setup/lang/ directory.