|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Do not translate or Exclude? - 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
|
Hi, What's the practical difference between selecting a string and set it to "Do not translate" and excluding it using Exclude (Ctrl+E)? When should I use one over the other? Thanks /Frede
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Frede, Here is the info from the online-help: http://www.sisulizer.com/online-help/WorkingWithTranslationSheet.htm Excluding rows When Sisulizer reads the original sources it extracts all the resource data that has been selected to be scanned. Sisulizer processes the resource data and adds the rows and visual elements if needed. Sometimes there are rows visible that you don't really want to have there. Either they need not the be translated or they are not translated at this point. Sisulizer has many ways to exclude data from the projects.
Do not translate Sometimes you don't want to remove or exclude a row but you just want to disable translating of the row. To do that you can mark any row as Do not translate. Such a row is shown on the sheet but can not be edited. Use Row | Do Not Translate menu to mark row as Do not translate. If row has been set as Do not translate it has some locked image on flags column on the left side of the sheet. The difference is, that Do not translate rows are scanned but shown as locked in the grid while excluded rows are not scanned and not displayed. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Frede Member
|
So the effect on generated translated files are the same. I guess that if I see a string for example that I know should never be translated I should exclude it instead of just saying do not translate. Can you give an example of when using do not translate would be appropriate over exclude?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Frede, Some think that e.g. SQL commands should not be translated and not shown. Some might think it is good if the translator does not translate them but see them for context reason. It is up to you what you prefer. Sorry, I do not have a golden rule for you. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
We do not use Do not translate at all on Sisulizer's localization projects. The only place I would use them is the case when I don't know if a string should be translated or not. In that case I would mark it do not translate. If no translator or tester complains then I can remove the lock and exclude the string. If I have control to the source and I could exclude the string from the resource I will do that. In that case teh string would not be in the resource and there would be no need to lock or exclude it. You localize SQL source code so you can also exlucde string by using string tagging 'Localize this' 'Do not localize this' --noslz In above the first line is scanned normally but the string in the second line is skipped. By default tagging is turned on and noslz acts as an exclude tag. Jaakko Attachment: Untitled.png (Downloaded 31 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Shortly: 1) Try to exclude string from the original file by removing it from resource or by tagging it 2) If this can not be done use excluding 3) Only after that you Do not translate Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Frede Member
|
OK, that makes sense thanks for clarifying.
|
||||||||||||||||
| |||||||||||||||||
| Current time is 08:52 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 > Do not translate or Exclude? | |
Sisulizer software localization tool - Three simple steps to localize
