As you may know we just moved all translation files including gadgets and core translations in to the languages directory as of version 0.9. The main benefits that leads to such a decision are:
Centralized manipulation of the translations
Individual repository for languages
To release the languages in a separate package which decreases the size of the main package
But after months of development, it seems there are some cons with the new structure:
Gadgets have lost their independency because EN as a base language is required in all gadgets
It sucks for gadget developers working on two different locations
EN translation is not optional and we need to include it in the main package for release
Github does not support common directory for two or more repositories and it made commits boring
My suggestion is to move back just the EN translations in to their gadget directory but with a new name e.g. Const.php or Translations.php or even en.php.
We need also to decide about Global.php, Date.php, Install.php and Upgrade.php. One idea is to move them to core and to their related directories too e.g. Install.php => install/en.php.
As you may know we just moved all translation files including gadgets and core translations in to the
languagesdirectory as of version 0.9. The main benefits that leads to such a decision are:But after months of development, it seems there are some cons with the new structure:
My suggestion is to move back just the EN translations in to their gadget directory but with a new name e.g. Const.php or Translations.php or even en.php.
We need also to decide about
Global.php,Date.php,Install.phpandUpgrade.php. One idea is to move them to core and to their related directories too e.g.Install.php=>install/en.php.