|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Completely excluding items - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Phils Member
|
Hi I am trying Sisulizer to scan a large VB6 source code project. It finds a lot of strings - and many of them must not be translated. Examples are file paths, DLL names, constants, codes used for simple encryption keys, keys for INI files, etc. I can exclude these from my project, and I can uncheck the option that allows the translator to see my source code. But in the translation edition the user can uncheck the option to Hide Excluded Strings, and they all become visible again. I can use the noslx tag, but I think that does the same as excluding the strings in the Sisulizer window. Is there a method of completely stopping these unwanted strings from being included in the project file shipped to the translator? If I export to an Excle file they are not included. If not, is it possible to stop the translator from making them visible? I would be happier if the strings were not included in the project file - this would stop the translaator (who is also our customer) from seeing anything that he should not see. It would also make the project file smaller. Best regards, Phil.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Hi, This "feature" that translator can uncheck hiding is a bug. I will fix it. It should be that only developer can check/uncheck it. Would this be good for you or do you want to re also remove excluded string totally away from project that are exchanged to translators. Jaakko Last edited on Tue Apr 24th, 2007 01:20 pm by Jaakko.Salmenius ____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Phils Member
|
Hi Jaako, It would be good if the translator is stopped from making excluded strings visible, but it would be better if it is possible to remove excluded strings from the project shipped to the translator. In the sle file you canot see the text, but when the translator opens and saves it they get an slp file and you can see a lot of the strings with notepad. We have a simple licensing mechanism for extra program features and I would like to hide these strings and some other items. I have not made an slp file of the full project yet, but it is going to be quite big! I think maybe 75% of the strings need to be excluded. At the moment I am thinking of sending an exported Excel file to the translators, but Sisulizer is a very nice program and I would be like to let them have the visual interface. Many thanks for your help Phil.
|
||||||||||||||||
| |||||||||||||||||
| Current time is 08:12 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 > Completely excluding items | |
Sisulizer software localization tool - Three simple steps to localize
