Congratulations to David for AMOS
Using AMOS tool for language pack translation
Congrats for the tool !
Thanks Nicolas. And sorry once again for false impression on having the pack 99% completed, it was a silly mistake in the calculations.
No problem. I see now better how much work remains
A question: the translation of the iso6393 and edufields files would me more easy to do outside AMOS. Is there any way to make it this way and import (ie. send you the files) afterwards?
First of all, I would like to say: David, one hell of a job. Second, I have to agree with Nicolas, that it would be more convenient, at least for some of the files, to be able to edit them outside AMOS? It's not a deal-breaker, just maybe a necessity from time to time
But overall experience is WOW!
I definitely agree with you guys - export/offline modification/import is on my todo list. There are just other more important issues to do now before 2.0 release so this has been postponed.
This and other improvements will come as funxtionality extension to the "Stage" part of AMOS. Simply said, the stage is the area where strings wait before they committed. But using the web Translator is just one way (though the only one implemented at the moment) how the translation can get to stage. Uploading a file or accepting a contribution sent by some other AMOS portal user are planned to be implemented as soon as possible.
Thanks for your feedback!
One more thing I have encountered during cleaning up of the outdated strings. Is there a possibility to add another option to the filter, named for instance: "Outdated strings only", so it would be a bit easier to either approve or change those outdated strings without going through a large number of missing strings (at least in my case)?
Thanks in advance
Well, the current filter settings "Missing and outdated strings only" is intentional. From my point of view, missing strings and outdated strings are similar as they both require translator's attention. The expected workflow for lang pack maintanance is that the translator comes from time to time to AMOS, asks for missing and outdated strings from all components and fixes them. Why do you want to fix outdated strings first and then add missing ones?
Actually, I would like all THREE of them to be present!
So you would have an option to check for missing AND outdated, and additional filter option bellow to check for outdated or missing strings ONLY.
Again, that is not a crucial issue, or something that has to be done right away, just something I thought would be useful for the future features