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: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
.Net: not importing new resource strings - 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 Mar 8th, 2017 02:03 pm
PM Private Upload Quote Reply
timbrown
Member
 

Joined: Mon Feb 27th, 2017
Location: United Kingdom
Posts: 8
Status: 
Offline
When we add new resource strings to the default resx files and scan for changes the new resources often don't come through and aren't available in the sisulizer project. The text then remains in English in the UI.

The is for a winforms project. Is there a property that need to be set in the UI or a way to force a refresh.

I'll be honest - this is a significant problem for us currently. It's responsible for a lot of application bugs.

Many Thanks

Last edited on Wed Mar 8th, 2017 02:04 pm by timbrown

Back To Top PM Private Upload Quote Reply

 Posted: Wed Mar 8th, 2017 02:34 pm
PM Private Upload Quote Reply
timbrown
Member
 

Joined: Mon Feb 27th, 2017
Location: United Kingdom
Posts: 8
Status: 
Offline
The winforms uses DevExpress components if that makes any difference. Thanks

Back To Top PM Private Upload Quote Reply

 Posted: Wed Mar 8th, 2017 02:39 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2869
Status: 
Offline
Can you please check that you scan the files in the right directory under Project - Edit Source - <your source>. Sounds like Sisulizer scans the wrong file.

Markus



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

 Posted: Thu Mar 9th, 2017 08:18 am
PM Private Upload Quote Reply
timbrown
Member
 

Joined: Mon Feb 27th, 2017
Location: United Kingdom
Posts: 8
Status: 
Offline
Thanks for the response. The source is a .Net solution file and is correct. Sisulizer isn't missing the entire resource file - it is missing some strings that are present in the default resx file and correctly bring through others. It's partially successful.

Any other thoughts on what coul dbe wrong?

Many Thanks

Back To Top PM Private Upload Quote Reply

 Posted: Thu Mar 9th, 2017 09:00 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2869
Status: 
Offline
Can you please send your slp and an old and new version of your resx showing the effect in a zip file. Use Private Upload to send them. We look into it.

Markus



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

 Posted: Thu Mar 9th, 2017 09:12 am
PM Private Upload Quote Reply
timbrown
Member
 

Joined: Mon Feb 27th, 2017
Location: United Kingdom
Posts: 8
Status: 
Offline
Thanks for this. I don;t think we can provide the entire solution. I'll work with the UI team to get a cut down version that shows this effect and send it on (once I've got permission from my boss). Many Thanks

Back To Top PM Private Upload Quote Reply

 Posted: Thu Mar 9th, 2017 11:39 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2869
Status: 
Offline
If the missing strings are "inside" the third party control Sisulizer (or any other localization tool) might be unable to scan these. There are third party controls that are translateable. For the others you have to set these strings at runtime from code. Read the strings text resources to make them localizable.

Markus



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

 Posted: Wed Mar 15th, 2017 11:18 am
PM Private Upload Quote Reply
timbrown
Member
 

Joined: Mon Feb 27th, 2017
Location: United Kingdom
Posts: 8
Status: 
Offline
Uploaded files as requested. There is a problem with a number of resource files - this is just an example. The resource

<data name="eyeLabel.Text" xml:space="preserve">
<value>Eye<color=255,0,0>*</color></value>
</data>

doesn't come through to the project after a scan.

If I add additional resources to the same resx file and rescan then it does come through. One of our developers strip back the solution (sln) then created a new slp project then rescanned then the eyeLabel.Text file came through correctly.

Back To Top PM Private Upload Quote Reply

 Posted: Wed Mar 15th, 2017 11:21 am
PM Private Upload Quote Reply
timbrown
Member
 

Joined: Mon Feb 27th, 2017
Location: United Kingdom
Posts: 8
Status: 
Offline
Our developer looked at the xml in the slp file. The eyeLabel.Text was present but it wasn't visible in the sisulizer tool when the slp file was opened. These are his comments which you might find useful - Thanks

********

This is taken from the Medisoft.UI.EMR.slp file that is not bringing up the eyeLabel text for translation and is never pulled through to the French resource file

<component class="TVisDefaultControl" name="eyeLabel" state="0" created="20170125133225" type="Medisoft.UI.EMR.Presentation.Controls.Editors.Base.CHTLabelControl" parentfont="0">
<row id="Appearance.Font" class="TFontRow" state="0">Open Sans,8.25</row>
<row id="Location.X" state="0">2</row>
<row id="Location.Y" state="0">92</row>
<row id="Size.Height" state="0">26</row>
<row id="Size.Width" state="0">96</row>
<row id="Text" state="0">Eye<color=255,0,0>*</color></row>
</component>

Example of one that did work

<component class="TVisDefaultControl" name="statusLabel" state="0" created="20170125133225" type="Medisoft.UI.EMR.Presentation.Controls.Editors.Base.CHTLabelControl" parentfont="0">
<row id="Appearance.Font" class="TFontRow" state="0">Open Sans,8.25</row>
<row id="Location.X" state="0">2</row>
<row id="Location.Y" state="0">122</row>
<row id="Size.Height" state="0">26</row>
<row id="Size.Width" state="0">96</row>
<row id="Text" state="0" note="Status + red asterisk">
<native>Status<color=255,0,0>*</color></native>
<lang id="fr" date="20170227145615">Statut<color=255,0,0>*</color></lang>
</row>
</component>

This is an example of a brand new project with the same files and this one brings up the eyeLabel for translation and correctly knows we’ve already got the others translated.

<component class="TVisLabeledControl" name="eyeLabel" created="20170314121544" type="Medisoft.UI.EMR.Presentation.Controls.Editors.Base.CHTLabelControl" parentfont="0">
<row id="Appearance.Font" class="TFontRow">Open Sans,8.25</row>
<row id="Location.X">2</row>
<row id="Location.Y">92</row>
<row id="Size.Height">26</row>
<row id="Size.Width">96</row>
<row id="Text">Eye<color=255,0,0>*</color></row>
</component>

<component class="TVisLabeledControl" name="statusLabel" created="20170314121544" type="Medisoft.UI.EMR.Presentation.Controls.Editors.Base.CHTLabelControl" parentfont="0">
<row id="Appearance.Font" class="TFontRow">Open Sans,8.25</row>
<row id="Location.X">2</row>
<row id="Location.Y">122</row>
<row id="Size.Height">26</row>
<row id="Size.Width">96</row>
<row id="Text">
<native>Status<color=255,0,0>*</color></native>
<lang id="fr" date="20170314121517" status="2">Statut<color=255,0,0>*</color></lang>
</row>
</component>

Back To Top PM Private Upload Quote Reply

 Posted: Wed Mar 15th, 2017 04:17 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1928
Status: 
Offline
Thank you Tim for the samples. The reason that string (and some other) do not show up is they you have excluded those string values.

Choose Project | Excluded Originals menu. A dialog showing the excluded original values will appear. You can undo the exclude by selecting the value and clicking Remove and then OK.

Ilkka



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

 Posted: Wed Mar 15th, 2017 04:51 pm
PM Private Upload Quote Reply
timbrown
Member
 

Joined: Mon Feb 27th, 2017
Location: United Kingdom
Posts: 8
Status: 
Offline
Ah - thank you. That has brought the missing one up. Many thanks for your help

Back To Top PM Private Upload Quote Reply

Current time is 08:38 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > .Net: not importing new resource 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