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
Font not showing up in Dialog Viewer - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Wed Feb 1st, 2017 08:28 pm
PM Private Upload Quote Reply
lsirc
Member
 

Joined: Thu Jan 19th, 2017
Location:  
Posts: 12
Status: 
Offline
Not sure if I did something wrong. I uploaded a picture and my topic disappeared.

I want to do a preview of the dialog with MS Shell. Currently, Sisulizer shows it with a different font even though I have it set to MS Shell. My problem has not been fixed by removing "font" from excluded data types in Project -> Edit source.

The picture I have attached shows the issue. As you can see, the dialog viewer in Sisulizer is not correctly showing MS Shell. The difference is seen when you look at the dialog in Visual Studio or when you run the application.

I want the Dialog viewer to show the correct font. How can I achieve this?

Attachment: SISULIZERDIFFERENCE.png (Downloaded 21 times)

Back To Top PM Private Upload Quote Reply

 Posted: Wed Feb 1st, 2017 08:36 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
MS Shell is just a logical font. It is mapped to some other font by Windows. Please have a read:

https://msdn.microsoft.com/en-us/library/windows/desktop/dd374112(v=vs.85).aspx

-> Logical Fonts

What you see must be related to that.

Markus



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

 Posted: Wed Feb 1st, 2017 08:45 pm
PM Private Upload Quote Reply
lsirc
Member
 

Joined: Thu Jan 19th, 2017
Location:  
Posts: 12
Status: 
Offline
I understand that it is a logical font. However, in the resource editor in Visual Studio it shows up the same way as in the application.

It would be nice if I can get Sisulizer to do the same. Why can't I get it to map to the same font if its done by Windows?

Last edited on Wed Feb 1st, 2017 08:45 pm by lsirc

Back To Top PM Private Upload Quote Reply

 Posted: Wed Feb 1st, 2017 09:01 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
I'll have to aks R&D how it is done internally. Right now we just can guess what is happening.

Markus



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

 Posted: Wed Feb 1st, 2017 09:04 pm
PM Private Upload Quote Reply
lsirc
Member
 

Joined: Thu Jan 19th, 2017
Location:  
Posts: 12
Status: 
Offline
After further tests, I am also interested as to why the Dialog box is so much bigger in Sisulizer. If you look at my pictures, the Dialog in Sisulizer is a lot larger. I made the font the same and yet the Dialog box remains much larger.

Back To Top PM Private Upload Quote Reply

 Posted: Wed Feb 1st, 2017 09:07 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
Perhaps different fonts are used for calculation and rendering. We have to wait for R&D to check the renderer for issues with logical fonts.

Markus



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

 Posted: Thu Feb 2nd, 2017 01:21 pm
PM Private Upload Quote Reply
lsirc
Member
 

Joined: Thu Jan 19th, 2017
Location:  
Posts: 12
Status: 
Offline
Alright, thank you for your help and please let me know if you find out that there's something we can do.

I have another question that I'll post here instead of making another topic.

Is there any way I view the difference between two versions (say 2.1 and 2.0) where 2.1's slp file is an updated version of that of 2.0s?

Right now I use a simple Git difference tool, but I noticed that when you make changes to the slp file it likes to move things around. I'm not sure why it is moving things around, but it makes it really hard to tell what has changed. Any way around this or any other way of viewing the differences?

Last edited on Thu Feb 2nd, 2017 01:23 pm by lsirc

Back To Top PM Private Upload Quote Reply

 Posted: Thu Feb 2nd, 2017 01:38 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
The idea is, that if you use Sisulizer for your version 2 and then update your software to version 2.1 you do a Project Scan for Changes. Then Sisulizer will list everythng that is new, changed, deleted or stayed the sames with the reg, green, yellow and blue markers in the translation grid. So basically Sisulizer itselve acts as a diff tool for your sources. But is has no direct option to diff between two project files.

Markus



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

 Posted: Fri Feb 10th, 2017 02:17 pm
PM Private Upload Quote Reply
lsirc
Member
 

Joined: Thu Jan 19th, 2017
Location:  
Posts: 12
Status: 
Offline
Thank you for your responses.

I have another question. How do I know which dialog a string belongs to?

I have an .rc file with dialogs. I can find the string I want to translate, but I need to make sure it belongs to the correct dialog. Is there any kind of way to know other then going to find the dialog manually?

Back To Top PM Private Upload Quote Reply

 Posted: Fri Feb 10th, 2017 07:30 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


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

If a string belong to dialog item in a rc file you can right click on selected row in the sheet and click "Select node" in the context menu. It should redirect you to dialog node, if you are in a parent level in the Project Tree. Additionally, if you are in a parent node in the Project Tree, name of dialog should be visible as part of ontext name ("Context" column in the Shet). If you use Find/Replace feature Sisulizer automatically move you to specified sub-node (e.g. a dialog), when Sisulizer will find matched item. If you use "Find All" feature, selecting item on list in the "Find Results" pane will move you to specified node. There is no easy way to find specified node if string is e.g. in a Strintable and is linked to dialog.

Best regard,
Janusz



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

 Posted: Mon Feb 13th, 2017 07:53 pm
PM Private Upload Quote Reply
lsirc
Member
 

Joined: Thu Jan 19th, 2017
Location:  
Posts: 12
Status: 
Offline
Hi,

I know why my font, which is set to MS Shell Dialog is different in Sisulizer (maps to MS Sans Serif) and in my application (maps to Tahoma).

If you create a dialog in Visual Studio as MS Shell Dialog, it will automatically set the Style to:
STYLE DS_SETFONT | DS_MODALFRAME | DS_FIXEDSYS | WS_POPUP | WS_CAPTION | WS_SYSMENU

After a bit of searching, we found that if MS Shell Dlg is
set with DS_SETFONT and DS_FIXEDSYS, it will map to Tahoma instead of MS Sans Serif.

See here:
"If you want MS Shell Dlg to map to Tahoma, then you must also specify DS_SHELLFONT. DS_SHELLFONT is actually equivalent to DS_SETFONT | DS_FIXEDSYS."

http://microsoft.public.win32.programmer.international.narkive.com/yy9uK4nd/why-does-ms-shell-dlg-not-map-to-tahoma

So Sisulizer needs to check if DS_SETFONT | DS_FIXEDSYS are set in the style and map to Tahoma accordingly.

Can this be done? It would be really useful for testing purposes if I could see the correct font in the dialog preview.

Please let me know.

Back To Top PM Private Upload Quote Reply

 Posted: Thu Feb 23rd, 2017 07:32 pm
PM Private Upload Quote Reply
lsirc
Member
 

Joined: Thu Jan 19th, 2017
Location:  
Posts: 12
Status: 
Offline
Can I please have an update to this issue? Is there an ETA for this fix?

Back To Top PM Private Upload Quote Reply

 Posted: Thu Feb 23rd, 2017 07:32 pm
PM Private Upload Quote Reply
lsirc
Member
 

Joined: Thu Jan 19th, 2017
Location:  
Posts: 12
Status: 
Offline
Can I please have an update to this issue? Is there an ETA for this fix?

Back To Top PM Private Upload Quote Reply

Current time is 09:44 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Font not showing up in Dialog Viewer



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