The only translation mechanism that we consider when system is upgraded is web interface. All changes to the files fall into hack group, and hacks are problematic because they need to be maintained manually.
All upgrades include refreshed language indexes so they are overridden with latest version each time you upgrade. While dictionary files are not updated that frequently, this file is also updated during upgrade process.
What we recommend is to wait for the next releases to have fixes I said we'll have covered included and keep hacks at minimum or don't implement any of them. You can post comments and recommendations and we'll see to implement some of them that we consider to be beneficial. Once included by us in the system, tweaks become officially supported and you'll not need to worry about it when new updates are released.
PS: Thank you very much for the effort you put into reporting all these issues. We really appreciate your feedback and the next upgrade will have more complete localization support thanks mainly to comments and suggestions you posted.
As we're trying to keep our translation consistent, we've come across another issue.
The pop-op's for changing a user's avatar or a company's logo are inconsistent in their title. Both of them have the title "Change Icon" yet for the company it's a logo and for a user it's an avatar (look at the attachments). I found out it wasn't something I could change easily either.
What I did find out is that the pop-up's are generated by JavaScript in this file:
public/assets/modules/system/javascript/main.js - Line: 2284 - 2296
A little more consistency here. For each project module there's a special index page if no objects of that module have been added. As you can see from the attachment the messages aren't quite consistent:
- Tickets and Milestones are just as we want them.
- The rest do not include the link tag in the translation, which enforces all the translation of that bit to become part of the link. The easiest thing would be only to include the link reference in the translation so we can customize our play of word :)
As I was checking through the changes of aC 2.1.3 I noticed there are some problems with a few javascript error notifications:
- In public/assets/javascript/jquery.uni-form.js
- Line 164 should be changed from:
App.lagn('Value need to be a number');
- To:
return App.lang('Value need to be a number');
- Line 192 is missing return statement as well.
The module names listed when setting permissions for users getting added to a project are not consistent with the module name (see the attached image).
When looking at changing this I found a spelling error though irrelevant for the functionality:
All upgrades include refreshed language indexes so they are overridden with latest version each time you upgrade. While dictionary files are not updated that frequently, this file is also updated during upgrade process.
What we recommend is to wait for the next releases to have fixes I said we'll have covered included and keep hacks at minimum or don't implement any of them. You can post comments and recommendations and we'll see to implement some of them that we consider to be beneficial. Once included by us in the system, tweaks become officially supported and you'll not need to worry about it when new updates are released.
PS: Thank you very much for the effort you put into reporting all these issues. We really appreciate your feedback and the next upgrade will have more complete localization support thanks mainly to comments and suggestions you posted.