Community « Discussion forum « Localization support board « Facilitating translations - Just an idea «
Comment: Facilitating translations - Just an idea
| Next >> |
Jan: Actually, what you are suggesting is what is commonly proposed for software translation. A number of programs I worked on previously were structured this way.
For YACS, I have deliberately selected to depart from this scheme, because of the very high number of changes provided with each release.
A single language file is handy for the translation itself, but it adds on developer burden, because the centralisation of every string is really a tedious overhead.
Therefore, this makes sense when the set of features is quite stable. But this is not the case of YACS, which adds a bunch of new features on every release.
At the moment localization is achieved within each script, since this is the most straightforward approach for any PHP developer.
Note, however, that this could evolve later on to a centralized file for all strings, as soon someone will dedicate some time on this.
For YACS, I have deliberately selected to depart from this scheme, because of the very high number of changes provided with each release.
A single language file is handy for the translation itself, but it adds on developer burden, because the centralisation of every string is really a tedious overhead.
Therefore, this makes sense when the set of features is quite stable. But this is not the case of YACS, which adds a bunch of new features on every release.
At the moment localization is achieved within each script, since this is the most straightforward approach for any PHP developer.
Note, however, that this could evolve later on to a centralized file for all strings, as soon someone will dedicate some time on this.
by Bernard on Dec. 3 2005
