|
|||
|
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > How does Sisulizer create a context for text and xml files
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| How does Sisulizer create a context for text and xml files - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... | ||||||||||||||
| Author | Post | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
Frede Member
|
I need to translate strings in SQL scripts which seems to work OK by selecting "source code" as type. How does Sisulizer know the specific id (context) of each row so it does not mix up the translations when the script changes? I had a script with 10 rows and translated one row in SL. Then I added a new row in the script and rescanned I expected that everything would be shifted one row but SL correctly identified the previously translated row. This also works fine for XML files. Multlizer cannot handle this correctly but if you add content in the middle of the file everything below is shifted so the translation is useless. They recommended that you export the data after you did the translation and then import it again which will of course work but is somewhat cumbersome.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator 
|
When Sisulizer localizes source code (e.g. SQL script) it uses the original value as the context. This was choosen to make sure that the original file can change without the context needed to be changed as well. The drawback it that if you have the same string twice or more in your file, it will appear only once row in SL and all instances will get the same translations. Anyway this is quite rare situation. If you need different translatons you have to make sure that orignal values are different. Jaakko Last edited on Fri Sep 7th, 2007 09:13 am by Jaakko.Salmenius ____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Frede Member
|
So what happens if I modify an existing string in the original file. Will it keep the old translation or will I have to translate it from scratch (i.e. the translation will be empty once rescanned)?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
Sisulizer keeps the old translations even if you change your original source code. You will loose translations only if you change the original string. For exmaple str = "This is a samle"; -> str = "This is a sample"; You will loose the translation BUT str = "This is a sample"; -> myStr = "This is a sample"; SL keeps the translations
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Frede Member
|
I see, thanks for clarifying. This will do fine for us.
|
|||||||||||||
| ||||||||||||||
| Current time is 02:11 am | |
| Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > How does Sisulizer create a context for text and xml files | |
Sisulizer software localization tool - Three simple steps to localize
