export misses some XAML strings - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support

Support forum of the software localization tool Sisulizer

.NET, Delphi, ... - Sisulizer Localization Tool Support Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Not logged in - Login | Register

.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > export misses some XAML strings

Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius

Printer Friendly

export misses some XAML strings - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support

Author

Post

Posted: Thu Jul 2nd, 2009 10:31 pm

lachmayr
Member

Joined:	Mon Dec 1st, 2008
Location:
Posts:	33
Status:	Offline

I exported to .xls my XAML strings, but found Sisulizer missed content strings implicitly defined in elements. An example is:
<TextBlock x:Uid="TextBlock_2">Length:</TextBlock>

Will Sisulizer only export strings explicitly defined? An example is:
<TextBlock x:Uid="TextBlock_2" Content="Length:"/>

Posted: Fri Jul 3rd, 2009 10:53 am

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	1458
Status:	Offline

Hello,

Could you send to us your example XAML file via forum upload form?

Best regards,
Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Sat Jul 4th, 2009 09:03 pm

lachmayr
Member

Joined:	Mon Dec 1st, 2008
Location:
Posts:	33
Status:	Offline

Yes, I'll upload it.

Posted: Wed Jul 8th, 2009 12:53 am

lachmayr
Member

Joined:	Mon Dec 1st, 2008
Location:
Posts:	33
Status:	Offline

Actually, nevermind. Certain strings were not imported as 'translated' because the translated string was the same as the original.

Sorry about the confusion.

Posted: Mon Jul 13th, 2009 08:15 pm

lachmayr
Member

Joined:	Mon Dec 1st, 2008
Location:
Posts:	33
Status:	Offline

OK, so I think there is still a problem... I will upload an example file.

Posted: Mon Jul 13th, 2009 08:27 pm

lachmayr
Member

Joined:	Mon Dec 1st, 2008
Location:
Posts:	33
Status:	Offline

Hmmm... it would not let me upload my .xaml file in the Private Upload page, so I've pasted the contents here.

This XAML has some text boxes. Strings for each textbox appear as a row in the Sisulizer project.

However, only the first text box sets the 'text' field explicitly (eg. Text="Driver:" ), and so this is the only string to be added to the export file (.xls).

<fwrk:View x:Uid="fwrk:View_1" x:Class="ScanningWpfUI.DetailView"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns

="http://schemas.microsoft.com/winfx/2006/xaml"

    xmlns:fwrk="clr-namespace:Common.WPF.Framework;assembly=Common.WPF.Framework"
    xmlns:loc="clr-namespace:ScanningWpfUI"

    MinHeight="100" MinWidth="500" Loaded="View_Loaded">

    <UserControl.Resources>
        <ResourceDictionary x:Uid="ResourceDictionary_1">
            <ResourceDictionary.MergedDictionaries>
                <ResourceDictionary x:Uid="ResourceDictionary_2" Source="/Common.WPF.Resources;component/Themes/Normal.xaml" />
            </ResourceDictionary.MergedDictionaries>
        </ResourceDictionary>
    </UserControl.Resources>

    <Grid x:Uid="Grid_1">
        <Grid.ColumnDefinitions>
            <ColumnDefinition x:Uid="ColumnDefinition_1" Width="Auto"/>
            <ColumnDefinition x:Uid="ColumnDefinition_2" Width="*"/>
        </Grid.ColumnDefinitions>

        <Grid.RowDefinitions>
            <RowDefinition x:Uid="RowDefinition_1" Height="Auto"/>
            <RowDefinition x:Uid="RowDefinition_2" Height="Auto"/>
            <RowDefinition x:Uid="RowDefinition_3" Height="Auto"/>
            <RowDefinition x:Uid="RowDefinition_4" Height="Auto"/>
            <RowDefinition x:Uid="RowDefinition_5" Height="Auto"/>
            <RowDefinition x:Uid="RowDefinition_6" Height="Auto"/>
            <RowDefinition x:Uid="RowDefinition_7" Height="Auto"/>
        </Grid.RowDefinitions>

        
        <TextBlock x:Uid="TextBlock_1" Style="{StaticResource ItemValueNameStyle}" FontSize="25" Margin="0,0,5,0" Grid.Row="0" HorizontalAlignment="Right" VerticalAlignment="Center" Text="Driver:"></TextBlock>
        <Label x:Uid="Label_1" Style="{StaticResource ItemValueStyle}" FontSize="25" FontWeight="Bold" Grid.Row="0" Grid.Column="1" Content="{Binding Path=Driver, Mode=OneWay}" VerticalAlignment="Center" HorizontalContentAlignment="Left" />

        <TextBlock x:Uid="TextBlock_2" Style="{StaticResource ItemValueNameStyle}" FontSize="25" Margin="0,0,5,0" Grid.Row="1" HorizontalAlignment="Right" VerticalAlignment="Center">Status:</TextBlock>
        <Label x:Uid="Label_2" Style="{StaticResource ItemValueStyle}" FontSize="25" FontWeight="Bold" Grid.Row="1" Grid.Column="1" Content="{Binding Path=Status, Mode=OneWay}" VerticalAlignment="Center" HorizontalContentAlignment="Left" />

        <TextBlock x:Uid="TextBlock_3" Style="{StaticResource ItemValueNameStyle}" FontSize="25" Margin="0,0,5,0" Grid.Row="2" HorizontalAlignment="Right" VerticalAlignment="Center">Scanned:</TextBlock>
        <Label x:Uid="Label_3" Style="{StaticResource ItemValueStyle}" FontSize="25" FontWeight="Bold" Grid.Row="2" Grid.Column="1" Content="{Binding Path=ScannedTime, Mode=OneWay}" VerticalAlignment="Center" HorizontalContentAlignment="Left" />

        <TextBlock x:Uid="TextBlock_4" Style="{StaticResource ItemValueNameStyle}" FontSize="25" Margin="0,0,5,0" Grid.Row="3" HorizontalAlignment="Right" VerticalAlignment="Center">Sent:</TextBlock>
        <Label x:Uid="Label_4" Style="{StaticResource ItemValueStyle}" FontSize="25" FontWeight="Bold" Grid.Row="3" Grid.Column="1" Content="{Binding Path=SentTime, Mode=OneWay}" VerticalAlignment="Center" HorizontalContentAlignment="Left" />

        <TextBlock x:Uid="TextBlock_5" Style="{StaticResource ItemValueNameStyle}" FontSize="25" Margin="0,0,5,0" Grid.Row="4" HorizontalAlignment="Right" VerticalAlignment="Center">Length:</TextBlock>
        <Label x:Uid="Label_5" FontSize="25" FontWeight="Bold" Grid.Row="4" Grid.Column="1" Content="{Binding Path=Length, Mode=OneWay}" VerticalAlignment="Center" HorizontalContentAlignment="Left" />

        <TextBlock x:Uid="TextBlock_6" Style="{StaticResource ItemValueNameStyle}" FontSize="25" Margin="0,0,5,0" Grid.Row="5" HorizontalAlignment="Right" VerticalAlignment="Center">Confirmation ID:</TextBlock>
        <Label x:Uid="Label_6" Style="{StaticResource ItemValueStyle}" FontSize="25" FontWeight="Bold" Grid.Row="5" Grid.Column="1" Content="{Binding Path=ConfirmationId, Mode=OneWay}" VerticalAlignment="Center" HorizontalContentAlignment="Left" />

        <TextBlock x:Uid="TextBlock_7" Style="{StaticResource ItemValueNameStyle}" FontSize="25" Margin="0,0,5,0" Grid.Row="6" HorizontalAlignment="Right" VerticalAlignment="Center">Confirmed At:</TextBlock>
        <Label x:Uid="Label_7" Style="{StaticResource ItemValueStyle}" FontSize="25" FontWeight="Bold" Grid.Row="6" Grid.Column="1" Content="{Binding Path=ConfirmationTime, Mode=OneWay}" VerticalAlignment="Center" HorizontalContentAlignment="Left" />
    </Grid>
</fwrk:View>

Posted: Mon Jul 13th, 2009 10:12 pm

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	1458
Status:	Offline

Hello,

Yes you are right, your localizable resources are saved in your XAML file in two ways:
<TextBlock … Text="Driver:"></TextBlock>
<TextBlock … >Status:</TextBlock>
Sisulizer recognize string stored in "Text" attribute as "String" data type, while second example is recognized by Sisulizer as "XAML" data type – you could to test it by check/uncheck "XAML" and "String" data type in Sisulizer filter panel. Unfortunately, Export Wizard in current build can’t correctly recognize "XAML" data type, and for this reason you can export to XLS file only one string, that is "driver", because this item is recognized as "String" data type not "XAML". I’ll forward this issue to our R&D.
You could change structure of items in your XAML file from <TextBlock … >Status:</TextBlock> to <TextBlock … Text="Status:"></TextBlock>. It allows you export all strings to e.g. XLS file.

Best regards,
Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Mon Jul 13th, 2009 10:15 pm

lachmayr
Member

Joined:	Mon Dec 1st, 2008
Location:
Posts:	33
Status:	Offline

Thanks for looking at this.

Will there be a way for me to find out when this has been fixed? (besides reading release notes for each release).

Posted: Mon Jul 13th, 2009 10:16 pm

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	1458
Status:	Offline

We let you know about it via this forum thread.

Best,
Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Thu Jul 16th, 2009 11:01 am

Jaakko.Salmenius
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Espoo, Finland
Posts:	2178
Status:	Offline

Fixed in build 268. New build will come out in few days.

Jaakko

____________________
http://www.sisulizer.com - Three simple steps to localize

Current time is 10:07 am
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > export misses some XAML strings

WowUltra modified by Sisulizer Copyright © 2007-09 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize