Build 301 – you can now separately manage row and translation comments in Import Wizard
For improving team work-flow, Sisulizer has implemented comments feature. That can really facilitate transfer of information between developers and translators. Generally, Sisulizer provides two types of comments:
- Row comments – developer can add some description or other useful information to each string in Sisulizer project
- Translation comments – also translator can add some information for developer/project author to each row
Because these feature are related to team work, management of these features was implemented to Import Wizard. So, for import from Sisulizer projects you can select following behavior:
- Do not import
- Import if there is no comment at the moment
- Overwrite the current value
To build 300 you couldn’t separately manage here row and translation statuses and selected setting was applied to both status kinds . However, in some cases this solution was inconvenient. For example, developer has in his main project updated row comments, but at the same time he wants to update translation comments with newer version received from translator. However, if translator’s project contains also old version of row comments, during import row comments would be replaced by previous version of comments. For avoiding similar cases our developers implemented to build 301 separate management for both status kinds in Import Wizard. It gives you really flexible comments management.
Hint
One request for developers – don’t forget about adding comments to Sisulizer project. I know it is an additional job, but these comments with potential information about context, placeholders etc. can be very, very useful for translators.
Janusz
Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically to your feed reader.
[...] From build 301 you can manage it separately for both comment types. [...]