gregorerhardt
04-04-05, 11:49 PM
[I'm not often here in the forums, but I want to start this thread. Who wants to catch me should better email me]
This message goes out to all project admins, developers, translators and all interested people.
I'm a bit frustrated by the last translation strings updates over the last half year.
- developers often do not update the english reference translation strings if they add strings to dotproject (this makes the life hard for translators). In consequence I cannot use the translation utility in the system module because it is always incomplete.
- a second problem has emerged consisting in the fact that the module infos/strings are now cross-linked between often all other modules, so project strings now appear in files and vice versa (often caused by (automatic) tab inclusion or similar functionality copied to other modules) - it is IMHO now horrible for the translation maintainers to have the same stuff in three different places or moving stuff to common.inc.
I must admit that for the german loc I stopped using the modular .inc files and now I limited my additions to common.inc which makes it much easier to maintain. I know that this is expected to be much slower than the file per module method.
My proposal would be to move all translation strings for core modules to the central common.inc file and give up the deprecated module specific file for the core product.
The feedback amount for the german localization goes to /dev/null. Please give me feedback in all possible form. Throw bug requests for wrong or missing translations via the mantis bugtracker or mail requests to me!
This message goes out to all project admins, developers, translators and all interested people.
I'm a bit frustrated by the last translation strings updates over the last half year.
- developers often do not update the english reference translation strings if they add strings to dotproject (this makes the life hard for translators). In consequence I cannot use the translation utility in the system module because it is always incomplete.
- a second problem has emerged consisting in the fact that the module infos/strings are now cross-linked between often all other modules, so project strings now appear in files and vice versa (often caused by (automatic) tab inclusion or similar functionality copied to other modules) - it is IMHO now horrible for the translation maintainers to have the same stuff in three different places or moving stuff to common.inc.
I must admit that for the german loc I stopped using the modular .inc files and now I limited my additions to common.inc which makes it much easier to maintain. I know that this is expected to be much slower than the file per module method.
My proposal would be to move all translation strings for core modules to the central common.inc file and give up the deprecated module specific file for the core product.
The feedback amount for the german localization goes to /dev/null. Please give me feedback in all possible form. Throw bug requests for wrong or missing translations via the mantis bugtracker or mail requests to me!