Attachment: untitled.PNG (Downloaded 68 times)

Last edited on Wed Aug 15th, 2007 10:29 am by BStaack

Yes, that it is how it should be done. This way the automatic translation can work and you basically do not need any translation memory (TM). TM is used to re-use translations in a second project. It is intended to save to TM once you finished your job in project 1 and use it for translation once after you started project 2.

Just to make sure. In Sisulizer you do not need to make a second project if you have a new build of your software. In this case you simply use "Project - Scan for Changes" to re-use your translations.

You would only make a second project if you either fork your project (e.g. for some special OEM edition) or have a complete new second software.

The prefered way is to give all strings in one language in a seperate exchange package to one translator. The most translations companies work with freelancers not working in a team. To get the best terminology all strings in one language are translated by the same translator. If you have more than translator working at the same language they have to synchronize in their terminology. While a freelancer can translate 2000-4000 words a day even big projects are possible.

While translating Sisulizer itself to German we had been a team of three sales people and wanted to split the work because we are not full time translators.
We decided to do it the easy way and agreed to use copies of the full project and each translator worked in one area of the project e.g.: translator 1: all dialogs from a to g, translator 2: all static strings, .... Not very fancy but effective, easy and fast.
After all three translators finished their job we combined the project using the File - Import / Datei Import function. After that we used the strong filters of Sisulizer to find words which are translated differently by the translation team to get a consistent terminology.

But we´re a team of 3 localisators so we can´t share this project by working with it at the same time.  Maybe we could copy the project file and use it on different pc´s, but afterwards we can´t merge these 3 projectfiles back to 1.

As I mentioned the File - Import / Datei - Import function does that trick very easily :-)

You could also use the exchange wizard to split the project. But the way I described above by using simple conventions is easier. It has the charme, that if one translator is faster than the other they can simply agree to move the borders of their chunks. We simply did it in a way, that we said "Hey, I can also do dialogs from f to z also". As I said, not technical fancy but effective.

Team functions are already on our road map for the next major version (2.x). While most translators do not work in teams (even large LSPs hire a single freelancers for one language) we concentrated in other functions in v1 and left the more seldom used functions for v2.

I'm not sure about that. In Sisulizer you can have more than one language in one project. Simply add more if you like. You can even display more than one target language at the same time. Take a look at the View / Ansicht menu. Perhaps you give me some more details about this request.

Attachment: untitled.PNG (Downloaded 18 times)