|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Importing existing translations
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Importing existing translations
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Importing existing translations - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
carval Member
|
Hello, Sisulizer seems not to import translations if the translated value equals the original value even if the option to do so is activated. Do you offer training courses for Sisulizer? I still have big difficulties working with Sisulizer.  Thx for your help...
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Could you tell me something about your import source and import settings e.g. Import method etc. ? You can, for example attach to post some screenshot from "Import Wizard - Options". You can find some useful information about import options here: http://www.the-localization-tool.com/?p=67 Do you offer training courses for Sisulizer? I still have big difficulties working with Sisulizer. I recommend visit our blog with articles knowledge base: http://www.the-localization-tool.com and download our Quick Start Guide here: http://www.sisulizer.com/download2.shtml?filename=manual Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
carval Member
|
The main problem now is not what I asked earlier (beginning of thread). I inserted translations manually in VS. Those translations are located under properties/resources in resx files. If I start Sizulizer and "scan for changes" I get tons of not translated entries. Most of those entries are .text properties which do not need to be translated because they are already part of resx files in properties/resources. How do I exclude those from being translated once and for all? But I also get resource entries which are definitely already translated, but they show up as not being translated. Project/Import translations from localized files does not help.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, I would like find any advices for you, but I need to know your Sisulizer's project. Could you upload to us your Sisulizer project file and VS project files as ZIP via Private upload form? Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
crealogix Member
|
Hello, I've got the same problem. I have all resources builded, but in french there are loger texts so I edited them in VS2008 (make a button bigger) but in the Sisulizer project changed nothing. If I generate the project the Sisulizer resources overwrites my edited resources. thx for help
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Sisulizer's build feature always bases on source files and Sisulizer project contents. So if you edited your output file, this file will be replaced by new file generated during next build operation. However, if you edited output file e.g. resx file, you can import values from this file to your Sisulizer project. Go in Sisulizer to "File" menu -> "Import", select your edited output French file and optionally change "Overwirte method" setting. Of course, you need to do it before using Build feature in Sisulizer, because as I mentioned above, this feature replace output files. I've got the same problem. I have all resources builded, but in french there are loger texts so I edited them in VS2008 (make a button bigger) but in the Sisulizer project changed nothing. I highly recommend changing these values in Sisulizer project instead editing output Sisulizer files in Visual Studio. This is better and more comfortable solution. If you do it in Sisulizer, you needn't change these values in source files (changed sizes/positions are used only for selected languages) or edit output files. You can do it in Sisulizer in several ways e.g. via moving sizes in Sisulizer Visual Editor, typing appropriated values in translation sheet - that require checking "Integer number" item in Filter Panel (look on attached screenshot), etc.. More information about these features you can find in this http://www.the-localization-tool.com/?p=636 article on our blog. Best regards, Janusz Attachment: screen.png (Downloaded 8 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 06:19 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Importing existing translations | |
Sisulizer software localization tool - Three simple steps to localize
