|
|||
|
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) > Bugs and Quirks in Sisulizer > Local Namespace Prevents XAML Translation
|
|
|||
|
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) > Bugs and Quirks in Sisulizer > Local Namespace Prevents XAML Translation
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Local Namespace Prevents XAML Translation - Bugs and Quirks in Sisulizer - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
jlars Member
|
I have another technical problem I hope you can help with. For WPF, I sometimes use locally defined classes in the XAML. I am finding that these xaml files are not being translated by Sisulizer. Below I included an example. This xaml will not get translated by Sisulizer to baml in the resource DLL (I am using a vcproj file with Sisulizer.) However, if you remove the line: xmlns:local="clr-namespace:Datacard.ID.ICap it works fine. (Note that this xaml has some elements stripped out. I'm not actually using the "local" namespace, merely declaring it here). Any help? Thanks. Joe Larson <Window x:Class="Datacard.ID.ICap.WorkflowResultWindow" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:local="clr-namespace:Datacard.ID.ICap" Title="Workflow Result" Height="500" Width="500" BorderThickness="0" WindowStartupLocation="CenterScreen" Icon="/ICap.Center;component/Person.ico" ShowInTaskbar="False"> <Grid> <Grid.RowDefinitions> <RowDefinition Height="24" /> <RowDefinition /> <RowDefinition Height="32" /> </Grid.RowDefinitions> <TextBlock Name="WorkflowResultCaption" Background="DarkBlue" Foreground="White" FontSize="14" FontWeight="Bold" Padding="3,3,0,0">Result Properties</TextBlock> <ListView Grid.Row="1" Name="WorkflowResultList"> <ListView.View> <GridView> </GridView> </ListView.View> </ListView> <Button Grid.Row="2" Name="CloseButton">Close</Button> </Grid> </Window>
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Joe, can you please send me you vcproj and the resource DLL causing the problem to support (at) sisulizer.fi. We will try to reproduce that. I see you have more than one thread. Please send the files needed for each cases separately to the above email and mention the thread title so we can answer you in the thread. Internally the work is spread on different team members. Thanks for you help and understanding. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello Joe, I tested behavior of your WorkflowResultWindow XAML file sent to us with sample Sisulizer project based on your solution file, with existing in original line 'xmlns:local="clr-namespace:Datacard.ID.ICap"' and with removed this line, and I didn't noticed any differences in Sisulizer translation sheet for both version, however during build targeted files by Sisulizer I've got output message that ''local' is an undeclared namespace, but it could appear only in my sample project based on your solution file, because it could be incomplete. Of course, we will be continue our investigation. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
jlars Member
|
Thanks for your feedback. Just to be clear, here is a step-by-step way to reproduce the problem: - Create new Sisulizer project based on ICap.sln. Accept all default settings, choose French language translation. - Within ICap.Center.csproj source, select workflowresultwindow, and translate the Title (English: Workflow Result) to French. Save the .slp file. - Select ICap.sln in Project Tree, right-click and select Build Item. In Output window, note that no error occurs while building ICap.Center.resources.dll. - On the hard drive, look at the ICap.Center\obj\Debug folder and note that there is no WorkflowResultWindow.fr.baml. There is, however, a MainWindow.fr.baml file. This suggests that no French baml is being generated for WorkflowResultWindow.xaml. (There are more steps I take to run the program with the Sisulizer output to see there is no French translation, but I'll skip that here.) - Now open ICap.sln with VS.NET (we use VS.NET 2008, 3.5 SP1) and remove these lines from WorkflowResultWindow.xaml: xmlns:local="clr-namespace:Datacard.ID.ICap" <GridViewColumn.CellTemplateSelector> <local:WorkflowResultTemplateSelector /> </GridViewColumn.CellTemplateSelector> - Rebuild the solution in VS.NET to verify WorkflowResultWindow.xaml is still valid. - Back in Sisulizer, rebuild the project. - On the hard drive, again look at the ICap.Center\obj\Debug folder and note that there IS a WorkflowResultWindow.fr.baml file. Thanks Again, Joe Larson
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hi Joe, Thank you for detailed info. Your post confirmed results of my tests, and files aren't compiled, because ''local" is an undeclared namespace. Below is my output message concerned to this issue (in message are info about "PL" versions, because I have created sample Sisulizer project based on your solution file for Polish language). I wrote my previous post, because I wasn't 100% sure whether I understood correctly your question, and I thought your question is additional concerned to localizable strings of WorkflowResultWindow file unavailable in the Sisulizer, and your info clarified it. Of course, we will be continue investigation, and we let you know about results. Could not compile the resource file: Microsoft (R) Build Engine Version 2.0.50727.1433[Microsoft .NET Framework, Version 2.0.50727.1433]Copyright (C) Microsoft Corporation 2005. All rights reserved.Build started 9/9/2008 9:28:45 AM.__________________________________________________Project "C:\Solution\ICap.Center\SlCompile0.proj" (ResolveReferences;MarkupCompilePass1 target(s)):Target MarkupCompilePass1: C:\Solution\ICap.Center\WorkflowResultWindow.pl.xaml(21,26): error MC3000: ''local' is an undeclared namespace. Line 21, position 26.' XML is not valid.Done building target "MarkupCompilePass1" in project "SlCompile0.proj" -- FAILED.Done building project "SlCompile0.proj" -- FAILED.Build FAILED.C:\Solution\ICap.Center\WorkflowResultWindow.pl.xaml(21,26): error MC3000: ''local' is an undeclared namespace. Line 21, position 26.' XML is not valid. 0 Warning(s) 1 Error(s)Time Elapsed 00:00:00.54 Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
jlars Member
|
I'm surprised you are getting this error. I don't see this error in my Sisulizer Output window. I am running Sisulizer build 270. Is there some other window or config setting that would allow me to see this error? -Joe
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
You can to export all entries of output window for latest operation to HTML file by click first icon (Show report) of Output panel toolbar, you can also copy contents of Output panel to clipboard by click second icon (Copy to clipboard). If you want to see, or export entries for previous operations, you should click fourth icon (Show history) of Output panel toolbar, and after click this icon you will see dialog window with list box of all operations at the top of window. If you select some operation, you can to see all entries for this operation at the bottom part of window (look on screenshot). You can configure history settings by click last icon (Edit properties) of Output panel toolbar. BTW: Could you send your output report for your project on support (at) sisulizer.fi? Best regards, Janusz Attachment: screen.png (Downloaded 40 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
jlars Member
|
Sorry I haven't replied sooner. I was busy with some other development. I think I see the reason for your build error ("local" is an undeclared namespace). After removing the line: xmlns:local="clr-namespace:Datacard.ID.ICap" you must also remove the lines: Please try this, and you will now see Sisulizer generate the WorkflowResultWindow.fr.baml file. This file does not get generated when these lines are included in the xaml. I will send my Sisulizer report to support (there is no error reported while building ICap.Center, though). (BTW, is there a way to tell Sisulizer not to complain "XXX has no name"?) Thanks, Joe Larson
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
jlars Member
|
I don't know what happened during my last reply (I did a Quick Reply and used copy/paste), but part was lost somehow. It should say... Please remove the lines: <GridViewColumn.CellTemplateSelector> <local:WorkflowResultTemplateSelector /> </GridViewColumn.CellTemplateSelector>
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
Yes, I already tested your Project with removed these lines, and I know Sisulizer correctly build WorkflowResultWindow.XX.baml file. I sent results of my short investigation to our R&D, but I don’t know why we have got different output reports. I received already your file and I will begin to analyze it but unfortunately, I am out of home and now I work on PC without installed .NET SDK, and for this reason I can’t to repeat some tests, but I will do it after my come back, and of course I will forward results to our R&D. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator 
|
jlars wrote: However, if you remove the line: The problem was that XAML file used assembly files that were not part of standard .NET or WFP but your own (ICap.WorkflowDesigner). Sisulizer did not used them when compiled XAML to binary BAML. I am currently fixing this and it should be ready in few days. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
I fixed this in build 272. The new build will come later this week. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
jlars Member
|
Thanks. I will try 272 when it comes out. -Joe
|
|||||||||||||
| ||||||||||||||
| Current time is 12:28 pm | |
| 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) > Bugs and Quirks in Sisulizer > Local Namespace Prevents XAML Translation | |
Sisulizer software localization tool - Three simple steps to localize
