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
Text wraps in release but not in Sisu. No verification error. - 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: Mon Feb 11th, 2019 04:04 pm
PM Private Upload Quote Reply
Bill Auerbach
Member
 

Joined: Wed Jun 3rd, 2015
Location:  
Posts: 30
Status: 
Offline
Hello,
Ver.4 Rel 374:
Text will be OK and not wrap a line in Sisulizer but at runtime there is a wrap losing the bottom line.  We need a pad or tolerance value to force Sisu to also wrap in the dialog editor.
Fortunately, I caught this before release but I do not have the time to check every dialog in every language.  I really need this clipped text validation to be solid.

Shown in the attached picture.
Thank you,Bill

Attachment: Sisu_wrap.jpg (Downloaded 5 times)

Back To Top PM Private Upload Quote Reply

 Posted: Mon Feb 11th, 2019 04:43 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3261
Status: 
Offline
Dear Bill,

You can see in the translation sheet if a text becomes longer in the translation than in the original. If a cell becomes red you might want to check your application. The darke the red the more difference is between original and translation. You also can filter for this rows.

Hope this helps

Markus



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

 Posted: Mon Feb 11th, 2019 04:59 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3866
Status: 
Offline
Markus.Kreisel wrote: Dear Bill,

You can see in the translation sheet if a text becomes longer in the translation than in the original. If a cell becomes red you might want to check your application. The darke the red the more difference is between original and translation. You also can filter for this rows.

Hope this helps

You can also use Sheet filter for this. Click "Filter..." icon on Filter pane toolbar. Go to "Text" tab and specify desired value for "Long threshold". After specifying this settings, e.g. as 120% or 150%, sheet will display only rows with translations longer than originals based on this value.

Attachment: lenght_threshold.png (Downloaded 4 times)



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

 Posted: Mon Feb 11th, 2019 06:56 pm
PM Private Upload Quote Reply
Bill Auerbach
Member
 

Joined: Wed Jun 3rd, 2015
Location:  
Posts: 30
Status: 
Offline
Markus and Janusz,

Thank you for the fast response - your support of Sisulizer is far above that of other programs I use.

I will play with these ideas. My issue is, that it looks perfect in the Sisulizer Dialog editor but is displayed at runtime wrapped and losing a line.

Even if I use the view or a filter, this is still a manual process of over 90 dialogs in this program which is in 6 languages. I need the tool to find problems for me. Verification is my last and valuable step before I "F6" my program. Without a verification error, I can't tell if this has happened in any dialog in any of the languages.

You don't believe this is a problem if the text doesn't wrap in Sisulizer (thus there is no warning) but it does wrap when I run the program with the Sisu created DLL?

In other words, why are the 2 screen captures not identical?

Thank you,
Bill

Back To Top PM Private Upload Quote Reply

 Posted: Mon Feb 11th, 2019 09:07 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3261
Status: 
Offline
Dear Bill,
Sisulizer uses the same windows routines to simulate the look in your application. But its still a simulation. There are so many factors why your actual display renders different.

I assume it will be just a pixel or two causing a different word wrap.
Perhaps there is border or margin setting at runtime Sisulizer can't see in the resources? Something set in code or by MFC or .NET runtime. Or a different font handling.

It is a good idea to give things more room - not only for localization. What if your customer uses larger font scaling. Or accidently uses different system font.
Then the word wrap will also be different. Pewrhaps it is a good idea to have controls that add scroll bars in case the text becomes to long.

Markus




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

 Posted: Mon Feb 11th, 2019 09:20 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3261
Status: 
Offline
Hi Bill,
take a closer look. Your text fields are sunken while the display in Sisulizer shows them flat. This makes two pixel difference in width and height. I guess Sisulizer can't see this setting in the resouces and that is making the difference. If you are short in space it might be a good idea to switch off the 3-D look of the labels.
Anyway  I ask R&D about that
Markus



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

 Posted: Tue Feb 12th, 2019 12:57 pm
PM Private Upload Quote Reply
Bill Auerbach
Member
 

Joined: Wed Jun 3rd, 2015
Location:  
Posts: 30
Status: 
Offline
Hello Markus,

You saw what I didn't and you're right, we use the WS_EX_STATICEDGE on almost all static text objects. This is MFC as you also picked up on.

Regarding the customer changing fonts or the sizes, true, we'll have problems. But this is something he changed. As long as we're not missing lines of text in a pristine install all is good. I don't know how to make a static text scrollable without a custom control.

In any case, if Sisu applied the WS_EX_STATICEDGE I believe everything would work because it would wrap in Sisu as it does at runtime. Even if I allow more space, a translation could shift into this 2-pixel area, not wrap in Sisu, and then not be detected by verification.

If you can enhance Sisu for this that would be awesome. I can wait for an update but would also welcome a beta or engineering release. I'm sure there are occurrences of this happening in languages where I don't (or in some cases cannot easily) open a dialog to check.

Thank you for your persistence to see why this occurred.

Best regards,
Bill

Back To Top PM Private Upload Quote Reply

 Posted: Tue Feb 12th, 2019 01:54 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3261
Status: 
Offline
I ask R&D if there is a technical reason why this setting did not find its way to tge WYSIWY rendering.

Markus



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

Current time is 01:23 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Text wraps in release but not in Sisu. No verification error.



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

Impress - Privacy statement

Sisulizer software localization tool - Three simple steps to localize