|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Translate WPF BAML resources from satelllite assemplies
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Translate WPF BAML resources from satelllite assemplies
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Translate WPF BAML resources from satelllite assemplies - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
kostyash Member
|
Dear Support, We are evaluating Sisulizer Localization Tool to buy it and have already contacted you (by email) with this issue but the answer was not clear and hasn't solved our problem. So I'd like to ask our question here in the forum. Our GUI client was written using WPF technology in VS2008. We are trying to translate BAML resources (xaml controls, xml files, strings, etc) in satelllite assemplies (dll) that were created automatically under \Debug\he-IL folder (original language is Hebrew) since we defined the following property in each project file of the solution: <UICulture>he-IL</UICulture> . We are trying to translate our product to English version and despite the fact that Sisulizer has passed two first steps: Scan and Translate successfully and we've saw all necessary strings translated to English on the right-side pane, the output satelllite assemplies have been created under \Debug\en-US folder don't contain any translated strings we saw on tool's screen (it has been created by clicking on Menu->Project->Build All Sources in Selected Language) Why ? What was wrong ? I'd also like to ask about the answer we got from you in my last correspondence : > - Make sure you gave Sisulizer your .sln or .csproj/vbproj file so it can collect all information needed for a complete localization. My question is: Creating Sisulizer project I select all my satelllite assemplies (dll) under \Debug\he-IL that were composed of hebrew strings. Should I give .sln (.sproj) file to Sisulizer project together with all dll files represented my resouces ? Thanks in advance for your help Kostya Synel Company
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
kostyash Member
|
One additional comment: using LocBaml, well-known free WPF localization tool, I can translate all resources (strings) from satelllite assemplies without any problems.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Kosty, Perhaps there is some basic misunderstanding. But your post might have the missing information. Do you perhaps try to localize a previous localized assembly and not the original source? The general way is, that you scan in you .sln or .csproj and Sisulizer finds all needed source files. Then you add your translations and Sisulizer creates the assemblies in the subdirs. If everything works correctly there is no need to add extra files to the project. Do not add already localized assemblies to it. If you scan your .sln Sisulizer should find already existing assemblies and offer to import existing translations from it. This all should be automatic. If that does not work a problem might have occurred. So if above does not help, please zip your Sisulizer project plus your binaries and the sln file and use the private upload button above this post to send the file to us. we take a look why it does not build. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Markus.Kreisel wrote: If you scan your .sln Sisulizer should find already existing assemblies and offer to import existing translations from it. This all should be automatic. If that does not work a problem might have occurred. More information about import from already localized files you can find in this http://www.the-localization-tool.com/?p=295 article on our blog. If Sisulizer during project creation can't automatically import translations from already localized files (files are in other folder), try do it manually. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 06:10 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 > Translate WPF BAML resources from satelllite assemplies | |
Sisulizer software localization tool - Three simple steps to localize
