|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Row status and multiple languages
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Row status and multiple languages
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Row status and multiple languages - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Frede Member
|
I am a bit worried that there is a bug with setting the row status but I must first verify that it works the way I expect it to. Is the row status saved for each translated language or for all languages at the same time? E.g. if I clear the Changed status on a row, will that effect all languages or only the language I am currently editing. Surely it should only effect the current language and not all. I have made several changes in my project and have cleared the changed flag for all changes rows in that language. Now, when I want to view changed rows for other languages they don't return anything, indicating that this flag was also reset on these languages. Can you please clarify on how the row status is supposed to work Regards Fredrik
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Frede, the row status shows that an item in your sources has been changed. So it belongs to the original column. If your source changes and you use "Scan for Changes" Sisulizer will find these new, deleted and changed columns and marks them with yellow, blue, green or red markers. So if you translate you only have to translate the new (yellow bullet) rows and check the changed (red bullet) rows in all languages. If you removed some strings in your source Sisulizer will also find them and mark them as unused (blue bullet). All other items will be "in use" (green bullet) to show you that Sisulizer re-used the translations from the previous build of your source. While there is only one original language in your sources there is also only one row status. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Ilkka.Salmenius Administrator 
|
1.6.15 there is a new translation based property: "Invalidated". It is marked with a red dot. It will turn on when the original value has been changed (row has a changed status). Invalidated statuses remain even if you clear all the rows changed statuses. Invalidated turn off automatically when you modify a translation in any way. Or you can turn it off manually by a popup menu. regards Ilkka Attachment: Changed.PNG (Downloaded 20 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Frede Member
|
That's very wrong I believe. For example, we translate from the original English to Swedish internally but an external translator translates to German. With every change to the project we internally translate and clear the changed flag, otherwise we will have no idea what strings we verified to be correct and which ones needed to be changed from one build to another. Since we clear the change flag the external translator has no way of verifying German translations cause she can't see what rows that were changed from the last time we exchanged the project. This property should definitely be saved per language I believe. The invalidated option added in 1.6.15 is of course helpful but in our case we have already cleared the change flag before 1.6.15 was released.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Frede, why don't you use the Translation Status for that? This is stored seperatly for each target language and is made to track the status of the translation. The row status reflects only the status of your source code and must be the same for all languages because if you change or add one string in your souce code all translations have to be checked for that. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Frede Member
|
Markus, Well in that case, what is the point with the changed flag? What process do you suggest that I follow with each scan?
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Frede, after you did Scan For Changes you look if there are new or changed rows. If so, you create one Translation Packages for each of your translators. Each of them now has an own row status in his file. They have to translate New rows and check all Changed rows. They set the translation status to Translated. With 1.6.15 it becomes even a bit more logical because the translator only has to deal with translation status and can ignore the row status: After you did Scan For Changes you look if there are new or changed rows. If so, you create Translation Packages for your translators. They have to translate all rows with the translations status Untranslated and check all with the translation status Invalidated. They set the translation status to Translated. After you received and imported back all translations you should check the trabslations and set them to Complete, then you can build the new version of your software. Before you use Scan for Changes again you should reset the row statuses. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Thank you Ilkka for explanation of "Invalidated" item. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Frede Member
|
Markus, I think you're right and this is the way it must be done. I wish I had known it worked this way before I cleared the flag 8-/. Is there any way to determine what strings that changed from the current project to a project file I got back from the external translator earlier? This doesn't have to be in Sisulizer but can be in Excel/SQL Server or whatever, just so I can set the correct translation status for the changed rows.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Frede, actually clearing the changed flag was a bad idea. And guess what, it happened to me also once while translation Sisulizer to German :-( If you forget to check the changed items before you clear the flag there is no chance later to find them. The new "Invalidated" translation status in 1.6.16 is a very good and needed feature. Sorry, there is no undo for removing that flag: http://www.sisulizer.net/view_topic.php?id=154&forum_id=4&highlight=new+clear Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 07:57 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Row status and multiple languages | |
Sisulizer software localization tool - Three simple steps to localize
