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.

Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 

 Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
[WPF] Text set by triggers is not picked up by sisulizer - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Wed May 5th, 2010 04:25 pm
PM Private Upload Quote Reply
bikedude
Member
 

Joined: Thu Aug 20th, 2009
Location:  
Posts: 79
Status: 
Offline
I have some XAML code where Sisulizer only picks up three strings.

My (unhelpful I admit) guess is that it doesn't like triggers like these:

                        <Setter Property="Text" Value="The marc record(s) has items on different units." />
                        <Style.Triggers>
                            <DataTrigger Binding="{Binding Path=HasUserAccessToAllItems}" Value="False">
                                <Setter Property="Text" Value="The marc record(s) has items on different units, also units that isn't accessible." />
                            </DataTrigger>
                        </Style.Triggers>


Entire xaml file attached as a private upload.

Back To Top PM Private Upload Quote Reply

 Posted: Thu May 6th, 2010 05:37 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
Fixed in build 304. New build will come out this week.

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Thu May 6th, 2010 06:53 am
PM Private Upload Quote Reply
bikedude
Member
 

Joined: Thu Aug 20th, 2009
Location:  
Posts: 79
Status: 
Offline
Thx again, Jaakko!

Back To Top PM Private Upload Quote Reply

 Posted: Wed May 19th, 2010 08:53 am
PM Private Upload Quote Reply
bikedude
Member
 

Joined: Thu Aug 20th, 2009
Location:  
Posts: 79
Status: 
Offline
We upgraded to build 305 and we noticed something we've not seen before:

  L:\Flamingo\Main\src\Windows\WPFForms\roILLReadRequestFromWebDialog.sv-SE.xaml(162,87): error MC3094: Cannot convert string value 'Röd' to type 'Brush'. [L:\Flamingo\Main\src\Windows\WPFForms\roILLReadRequestFromWebDialog.proj]

It feels as if the new build of Sisulizer picks up more than before, even of stuff that is not relevant. A bunch of properties (like brushes and the "visibility" property) were auto-translated to various languages. These languages won't build unless we manually clear them again.

We've tried excluding properties, but it seems a project-wide exclusion of e.g. the "Visibility" property is not possible? (It's only excluded for that component instance?)

Back To Top PM Private Upload Quote Reply

Current time is 08:43 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > [WPF] Text set by triggers is not picked up by sisulizer



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