|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Translating Silverlight Applications
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Translating Silverlight Applications
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | Page: 1 2   |
|
|||||||||||||||
| Translating Silverlight Applications - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
rolffux Member
|
I'm evaluating Sisulizer and I'm trying to localize a simple Silverlight 2 Application (see attachment). I tried once a Sisulizer project on a "project base" (Attachment SimpleProject.slp) and once on a binary base (selected the XAP as source, Attachment SimpleBinary.slp) I had no success with both approaches. I added an attachment with the simple Silverlight project and both Sisulizer projects. Appraoch on a project base: XAML:
Problem 1: I don't see the ComboBoxItems for translation. I played with components, properties and keywords, but I had no success. Problem 2: Sisulizer couldn't compile the translated XAML file Approach on a binary base (selected the XAP file in Sisulizer): Problem 1: I see all attributes from XAML (Height, Width etc.) for translation. I can manually suppress them, but is there a possibility to filter them? I could filter only one expression at the same time. Problem 2: Opening the generated Testpage for the XAP shows me only the Sisulizer language switch but no application appears. (In the attachment run TestPage.html in the bin/debug/all directory) Maybe it is a Evaluation Version problem, because I saw Sisulizer replacing not translated XAML attributes like "Height" with "[Evaluation Version]", what would mean I cannot evaluate Sizulizer with XAML translation.... Attachment: Simple.zip (Downloaded 3 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi, There are some aspects in this case: The actual build 281 has problems with project base XAML and user controls. It is needed to use the binary approach. The pity is, that the binary approach also has some problems with XAML the next build will fix. It tried with the current licensed beta and I found that I have to send our R&D your files for a fix. While it is a build problem I make it urgent. Thanks for reporting that. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
There was a bug in 281 that caused Sisulizer to ignore XAML resources and to handle them as XML files. I fixed this in 282. Your .xap file contains the application file (Simple.dll) and manifest file (AppManifets.xaml) and German and English satellite assembly files. Remove the satellite assembly files from XAP. The idea is to create single language XAP and then Sisulizer creates a new XAP that contains the original files and satellite assembly file(s). Anyway you have to way for build 282 that will come out in few days. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
rolffux Member
|
Hello, Thanks, Build 282 solved the problems. I've still a question. I've the following XAML Code
The ToolTipService.ToolTip doesn't appear for translation. What do I have to do/configure? Is there a tutorial how to add custom properties for translation? Rolf
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Rolf, Look under Tools - Platforms - .NET - Components. There you find the settings needed. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
rolffux Member
|
I tried it, but it didn't work. Would it be possible to show me step by step what I've to do for the "ToolTipService.ToolTip" case?
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, I could also not manage to scan ToolTipService.ToolTip in
while it scans fine here:
I asked our R&D for some hint. If it is urgent you could use the second syntax as a workaround. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
rolffux Member
|
Hi Markus, It's not urgent, because I'm in the evaluation phase, so I don't need the workaround. I noticed already, that the workaround works, but for me it is important, that a tool helps me to save time and I don't have to use workarounds. In a productive case with maybe 1000 Tooltips, it would be a mess at the end of a project to change all the Tooltip declarations. For us it is a requirement, that we can add/(remove) different (custom) properties in XAML for translation, otherwise the advantage of a localization tool is doubtful. Best Rolf
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Rolf, Sure. We just always try to give workarounds to our customers in case there is a deadline. In the moment we are exhibiting in San Jose and Tokyo so the final fix in Sisulizer might be delayed a bit. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
rolffux Member
|
Hi Markus, Isn't it possible to add any new properties at the moment or just the Tooltip? I tried to add the "Click" property/event of the Button class (I know it doesn't make sense, but just to try), but had no success either  Rolf
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Rolf, I also had no luck. Our R&D will look into it. Perhaps we both are just missing some information :-) Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
rolffux Member
|
Hi, what is the state of my problem? My evaluation time is over soon. Cheers Rolf
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
It tested this an on my window and Sisulizer scanned and localized ToolTip just OK. I am trying to figure out why does it not work on your case. Can you upload your user control (.xaml + .cs) to me? I take a look at it. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
rolffux Member
|
Hi Jaakko, I attached the whole project (Silverlight and Silsulizer). As already mentioned the tooltip works as attached property, but not direct as "ToolTipService.ToolTip" I added a custom TextBox control "MyTextBox" with a custom dependency property "MyText". I tried to add this custom component under Project->Components, but I had no luck. How can I add the MyText property for translation? Best Rolf
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Thanks Rolf. I am working on your sample. Today I improved ToolTips localization and premapped ToolTip and ToolTipSerivce.ToolTip controls. I will make sure than next build of Sisulizer can properly localized tooltips and your app. I also deleted your app after I downloaded it. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
rolffux Member
|
Hi Jaakko, Thanks, What about my custom control MyTextBox with the Property MyText? Isn't it possible to add custom controls/properties for translation? If it is possible, what did I wrong? How to do? In my opinion it is important to have such a feature. Otherwise I fear I'll have problems to translate productive silverlight applications... Cheers Rolf
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Rolf, I spoke with Jaakko and he is working on your issue. There might still exist a problem with user controls. Please gives us a few days to sort this out and make some tests. Generally you would fine tune your controls under Tools - Platforms - .NET - Components. But this does only work for components Sisulizer finds while scanning. It is not possible to influence the scanner in a way that it scans more elements. Silverlight is a pretty new platform and we at support have also get used to it :-) Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
rolffux Member
|
It didn't work over Tools - Platforms - .NET - Components neither. I hope Jaakko will fix also the problem with user controls/properties. It's really important for me. Rolf
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
>>It didn't work over Tools - Platforms - .NET - Components neither. Yes, if Sisulizer does not scan the component it is invisible and can not be fine tuned in that dialog. I hoped it would just be a setting but Sisulizer seems to be blind for that particular user control. >>I hope Jaakko will fix also the problem with user controls/properties. It's really important for me. I know that he isolated himself at the moment to fix two important issues we have. One of them is yours. He is fully concentrated at work will not give feedback himself in the moment. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
This problem was a lot easier to fix than I thought. The problem was the even Sisulizer let you map a WPF custom control it did not use the custom mapping. Instead Sisulizer always used the default (e.g. premapped) settings. I fixed this in 286. The new build will come out in a week or two. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 09:15 pm | Page: 1 2 |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Translating Silverlight Applications | |
Sisulizer software localization tool - Three simple steps to localize
