I’ve several translators for one language. How I can manage it?
Sisulizer is a flexible tool and allows managing similar situation in a couple of ways. I describe below some short workflow examples:
Exchange Wizard
You can use Exchange Wizard for selection specified resources sent to selected translators. In step “Exchange Wizard – Languages and Items” of Exchange Wizard select desired language (in our example Portuguese) and exclude undesired items in right panel by double clicking these items. The translator in our example will get only “String” resource from Delphi binary source. Then you can create next package for this same language and select other items e.g. CHM source and send this exchange package to another translator, etc.
Unfortunately, this solution can cause inconsistent translations e.g. different translations for identical originals. So you need after import translated packages select most appropriated translations for duplicates and generally review and verify content of whole project and it can take lot of time and work.
Comments using
You can also use “Row comment” column for assigning selected strings to specified translators. In this case you needn’t to split exchange package to separate parts. Just send to all translator this same file. With this solution each translator knows what strings he/she should translate. For doing it you need to click “Sheet columns” button on Translation sheet toolbar and move “Row comment” from “Hidden columns” to “Visible column”. Next type e.g. name/surname of translator to comment cell, copy this comment, select all appropriated rows and paste (multi-paste) comment to “Row comments” cells of all selected rows. Next repeat it for other translators. It still doesn’t solve issue of inconsistent translations and require some additional job, but I think this solution is more comfortable and flexible than solution with sending to translators exchange packages with selected sources or source’s parts. For example you always can control who translated selected string, because you see translator name sheet together with translated string. You can sort sheet contents by translations, context, but also by comments (names of translators). Additional, you can use any order (not only alphabetical order) to indicate translators their items for translate.
Because exchange package doesn’t remember sheet column layout, you should mention your translators how enable “Row comments” column in sheet view.
Language variants
Any time ago I coordinated some team of freelancers. They have been different habits, they used different terminology, and it really hindered our job. So in this case, I used solution with adding custom column for each translator. You can do it via adding custom language variants via “Tools” menu -> “General” -> “Languages” tab -> select translation language in left column and click on “Add variant”. Here type preferred names for your new language variant.
Next, add these created language variants to your project via “Project” menu -> “Language”.
After adding these languages to project and adding to visible columns, your sheet can look like on below screenshot:
Next you can send to selected translator package only with selected variant or with all variants. It depend only of your needs and preferences. After receiving translated project you import it to appropriated variant column in your project. Then, you can verify imported translations, select best translations of duplicates and copy verified translations to you main language column.
This solution has following pluses:
- You can keep different translations of this same string in project
- You can see and compare in one view translations received from all translations
- That allows you get very consistent translations
But also has minuses:
- You need one additional person to coordinate this job or dedicate your time for this work (verification, selection, copying translations to main language column etc.)
- It can really expand Sisulizer project size and slow down work with this project
Shared Translation Memory
If you and your translators use Sisulizer Enterprise edition, you can also create shared Translation Memory based on MS SQL Server or MySQL databases, but of course, you need t0 install these database(s) on your PC or other PC in your network. This solution allows working all Sisulizer users with one centralized, remote Translation Memory. Because Sisulizer allows on saving to Translation Memory several translations in this same language for selected string, you can select most appropriated translation during translation with Translation Memory. However, this is difficult because you need to know context and you should speak in selected translation language. You can find more information how add new Translation Memory and how manage it in this article in our blog.
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.
Comments
No comments yet.
Leave a comment