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.


 Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius  
AuthorPost
halley73
Member
 

Joined: Fri Aug 8th, 2014
Location:  
Posts: 46
Status: 
Offline
Hi,
I've a form with two buttons like this

https://ibb.co/jcUqDv

When I localize it with Sisulizer button are moved up like in the image

https://ibb.co/jPYvfa

What can be?

Thank you

Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
Hi,

perhaps you or your translater has set the Top value of the control by accident. Check that your filter that it shows integers in the grid and then check if the .Top or .Left properties have been set.

Sisulizer uses the original resources as a blue print and changes properties that are needed to localize. It can not change the layout except what is controlled by property values.

You also might want to look with a Resource Hacker (e.g http://www.angusj.com) with the localized files to see how the locslized resources looks like. You then can see if the resource is wrong or something is moving the buttons at runtime.

Markus

 

Attachment: 0075.jpg (Downloaded 64 times)

halley73
Member
 

Joined: Fri Aug 8th, 2014
Location:  
Posts: 46
Status: 
Offline
I've checked component properties by clicking on Property voice on the popup menu that I can visualize by right clicking on the button.
I don't know how to show property in main window as in your picture.
With my method I don't find any change in Top property of the button.

Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
Perhaps your project did not read Integers at all (its an option in the project settings).

Please zip your original, the localized binary and your .slp. Use Private Upload button right above this post to send the files. We'll take a look.

Markus

Janusz Grzybek
Super Moderator


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

Thank you for files. You are right, there are only 3 strings changed. Output file looks internally like original, but I can't test real behavior of this DLL with working application. I'll ask our R&D about this.

I don't know how to show property in main window as in your picture.
Check "Integer" checkbox in the Filer Pane. Here is article about common filter types: http://www.the-localization-tool.com/filter-panel-common-filters-for-translation-sheet/

With my method I don't find any change in Top property of the button.
You can also compare original and localized form directly in the Sisulizer. Right click on the form in the Project Tree and select "Show as Text" -> "Compare..." All differences will be indicated by red font. For comparing files you need first build output file. Here is article: http://www.the-localization-tool.com/comparing-source-and-localized-resources/

Best regards,
Janusz

Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
Hi,

I also made a quick test. I took the DLLs you send and made a new Sisulizer project from them (since dialogs are stored in resources Resource Hacker does not render).
Both looks the same from button positions etc. in the WYSIWYG of Sisulizer. Is there a slide chance that you change the button position or hide the cancel button in code at runtime?

Markus

Steve67
Member
 

Joined: Wed Feb 15th, 2017
Location:  
Posts: 16
Status: 
Offline
Hi,
I have the same problem in three different Delphi project.
The checkbox "integer" don't solve my problem in any case
Top property for any components is not visibile in Sisulizer Components->Property
I have controlled any options suggested in previous post without success

Any ideas ?

Best Regards,
Stefano Fanti

Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
Do you perhaps have a simple sample Delphi project (incl. source code) just consisting of such dialog that our R&D can look into it and debug it? If yes, can you please upload it using Private Upload.

Markus

Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
Can you also please share your Sisulizer build and the Delphi version you are using.

Markus

Steve67
Member
 

Joined: Wed Feb 15th, 2017
Location:  
Posts: 16
Status: 
Offline
Hi,
Sisulizer 4.0 Build 365
Embarcadero Delphi Berlin 10.1 update 1

My project is very complex and i can not be disclosed for security reasons.
Sorry...

I have made one project with only one form and in this case i had non problems
If I add one or more form the problem reappears.
Very strange ....

Best Regards,
Stefano Fanti

Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
A sample with three dialogs showing the issue would also help. As you said this is strange and we need to find a way to reproduce that.

Markus

Steve67
Member
 

Joined: Wed Feb 15th, 2017
Location:  
Posts: 16
Status: 
Offline
Hi,
I sent a portion of the project that has the problems
Thanks for collaborations ...

Best Regards,
Stefano Fanti

Steve67
Member
 

Joined: Wed Feb 15th, 2017
Location:  
Posts: 16
Status: 
Offline
Hi,
These are two images that confirm the fact that the Top property is not handled





Best Regards,
Stefano Fanti

Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1961
Status: 
Offline
For halley73:

Thank you for the same. However when I looked the TFormFilterCaption forms (original DLL and French DLL) the sizes and positions of both button were identical.

Two possible reasons

1) Is it some other form that show the problem. If yes please tell the name of the form

2) Do you move the button on runtime?

Ilkka

Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1961
Status: 
Offline
For Steve67:

Same thing here. I used your sample, created English EXE and then compared original and English TPasswordDialog form. They were identical. I see that your component do not have real positions in DFM but you do the layout on runtime (e.g. moves the control on the right places). Can you check that code if it works correctly.

Ilkka

Steve67
Member
 

Joined: Wed Feb 15th, 2017
Location:  
Posts: 16
Status: 
Offline
Hi,
Thanks for your reply

I checked all the source and Form are in the prescribed positions and I do not have code that moves them at runtime.
By controlling the DFM both visually (in the IDE of Delhi) and in text format the Top and Left properties are visible and are not changed at runtime.
If I try with a simple test program that contains a single Form, from Sisulizer I can see the same properties on the selected component which does not happen with the project I have sent.
In addition, the same problem is present in the previous build 364

Best Regards,
Stefano Fanti

Last edited on Thu Feb 16th, 2017 06:44 am by Steve67

halley73
Member
 

Joined: Fri Aug 8th, 2014
Location:  
Posts: 46
Status: 
Offline
Ilkka.Salmenius wrote:
For halley73:

Thank you for the same. However when I looked the TFormFilterCaption forms (original DLL and French DLL) the sizes and positions of both button were identical.

Two possible reasons

1) Is it some other form that show the problem. If yes please tell the name of the form

2) Do you move the button on runtime?

Ilkka


Hi Illka :-)

At the moment I don't have other form signaled by customer, so I don't know.
I've checked the code and I'm sure to not move the buttons a runtime.
It seem that the localized version don't consider the window title bar for top calculation.

halley73
Member
 

Joined: Fri Aug 8th, 2014
Location:  
Posts: 46
Status: 
Offline
Hi Illka,
I've found another form the have same issue uFrmSendDateToLis.

Thank you :-)

Steve67
Member
 

Joined: Wed Feb 15th, 2017
Location:  
Posts: 16
Status: 
Offline
Hi,
I wanted to know if there are any news about this bug
Before long I have to start working with a localization Sisulizer but in this situation I can not proceed.

Best regards,
Stefano Fanti

Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
At this time we can't reproduce it.

Can you please add some code to your dialog that outputs the location and the visiblity status of the missing button at runtime after the dialog is completely drawn (e.g. text log file). We need to find what makes the button disappear.

What happens if you set the location of the button at runtime. You could use that as a work around.

Markus

halley73
Member
 

Joined: Fri Aug 8th, 2014
Location:  
Posts: 46
Status: 
Offline
Hi Markus,
if this can help you, I've found that the problem, in my case, can be replicated if I set the Anchor button property to left, bottom.
I will send you my little sample program.

Thank you

Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
_(at)_Halley73

The buttons in your sample move vertical if you change the size of the dialog. Does that also happen in the original?

Since Sisulizer does not change the logic or source code there must be already something in your source code doing this.

Markus

Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1961
Status: 
Offline
Thank you for the sample. I managed to reproduce it. The problem is form scaling that Sisulizer turns off by default. You have to set Sisulizer to ignore form scaling.

Seen the screenshot.

Ilkka

Attachment: Untitled.png (Downloaded 45 times)

Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1961
Status: 
Offline
And addition to previous. TForm has Scaled property. By default its value it True. By default Sisulizer makes that False. We added that feature to prevent VCL auto scaling that messed up localized forms expecially when localizing to Asian languages.

In you case Sisulizer did not change Left, Top property but turned TForm.Scaled to False and this caused the problem.

Ilkka

halley73
Member
 

Joined: Fri Aug 8th, 2014
Location:  
Posts: 46
Status: 
Offline
Thank you very much, it works.

Now remain only the problem of post

http://www.sisulizer.net/view_topic.php?id=3710&forum_id=4&jump_to=22641#p22641

Regards, Luca

Steve67
Member
 

Joined: Wed Feb 15th, 2017
Location:  
Posts: 16
Status: 
Offline
Markus.Kreisel wrote: At this time we can't reproduce it.

Can you please add some code to your dialog that outputs the location and the visiblity status of the missing button at runtime after the dialog is completely drawn (e.g. text log file). We need to find what makes the button disappear.

What happens if you set the location of the button at runtime. You could use that as a work around.

Markus

Hi,
I checked all of the source of the project but by the positions of the buttons and other controls are not modified by code.
I enclose another example taken from the same project that has the same problem.
Under no circumstances from Sisulizer I can see the Top and Left properties of the selected component.
This does not happen if the project will have a single Form.

Best Regards,
Stefano Fanti

Janusz Grzybek
Super Moderator


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

Thank you for files. We'll check this.

Janusz

Steve67
Member
 

Joined: Wed Feb 15th, 2017
Location:  
Posts: 16
Status: 
Offline
Hi,
Any news about the problem I have reported ?
My company solicits me to begin the application translators

Thanks for collaboration

Best Regards,
Stefano Fanti

Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
This thread mixes two issues. Whicgh one do you mean?
One is solved (Button position) with the next build and one (Encoding) is still under investigation.

Markus

Steve67
Member
 

Joined: Wed Feb 15th, 2017
Location:  
Posts: 16
Status: 
Offline
Hi,
The question of the position of the controls has not been solved for me.
I sent another project with the same problem but I have not been answered.

Best Regards,
Stefano Fanti

Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
So the "Ignore Form Scaling" setting described by Ilkka some posts above does not help in your case?

Markus

Steve67
Member
 

Joined: Wed Feb 15th, 2017
Location:  
Posts: 16
Status: 
Offline
Hi,
Tanks for your response.
That's right, the scaling form reported by Ikka does not solve my problem.
I made other tests and provided a new project with the problem Janusz but I have not yet received a response.
I'm sorry to insist, but I absolutely need to solve this problem

Best Regards,
Stefano Fanti

Steve67
Member
 

Joined: Wed Feb 15th, 2017
Location:  
Posts: 16
Status: 
Offline
Hi,
News ?

Steve67
Member
 

Joined: Wed Feb 15th, 2017
Location:  
Posts: 16
Status: 
Offline
I'm sorry to insist, but I absolutely need to solve this problem

Best Regards,
Stefano Fanti

Steve67
Member
 

Joined: Wed Feb 15th, 2017
Location:  
Posts: 16
Status: 
Offline
Hi,
I have installed the build 366 and I redid the scan but the anomaly is always present.

Best Reagards,
Stefano Fanti

Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
Dear Stefano,

I'll ask R&D about it. What happens if you set the position of that button at runtime in your code? It could be a work-around so you can start without further waiting.

Markus

Steve67
Member
 

Joined: Wed Feb 15th, 2017
Location:  
Posts: 16
Status: 
Offline
Markus.Kreisel wrote: Dear Stefano,

I'll ask R&D about it. What happens if you set the position of that button at runtime in your code? It could be a work-around so you can start without further waiting.

Markus

Hi,

I'm sorry but this is not practical because it forces me to write unnecessary code. The Delphi IDE allows me to place controls it right point. This problem was already present in the previous build of Sisulizer.

Best Regards,
Stefano Fanti

Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
I understand. In this case we have to wait for R&D's solution.

Markus

Steve67
Member
 

Joined: Wed Feb 15th, 2017
Location:  
Posts: 16
Status: 
Offline
Hi,
Any news about the problem I have reported ?
My company solicits me to begin the application translators

Thanks for collaboration

Best Regards,
Stefano Fanti

Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1961
Status: 
Offline
Hi Stefano,

I found the reason. Sisulizer scanned you application as it would be a FireMonkey application. It does have the FireMonkey style resources (that Sisulizer used to detect Firemonkey) but all form resources are actually VCL. This is why the position are incorrect.

I will fix this ASAP.

Ilkka

Steve67
Member
 

Joined: Wed Feb 15th, 2017
Location:  
Posts: 16
Status: 
Offline
Hi Ikka,
Great !!!!
I look for the solution as soon as possible.

Best Regards
Stefano Fanti

Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3005
Status: 
Offline
Hi All,

Perhaps a good idea to open an own thread next time. The case was closed since the issue of the thread starter halley was already addressed. This way it took longer than it should for this issue having a different cause as we found now.

So folks don`t worry to start an own thread in case you found something similar and its not 100% sure that it is the same problem. You still can mention and follow the other thread.

Thanks

Markus

Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1961
Status: 
Offline
Hi Stefano,

Once you get the new Sisulizer build (367) do this
1) Open your project
2) Right click the .exe fiel in the project tree and choose Properties
3) Select VCL options sheet
4) Check VCL in the Framework radio group.
5) Close the dialog and rescan (Project | Scan for changes)

Now Sisulizer scans it as VCL and everythign should work normally.

Build 367 will be released next month but I will send you an internal build.

Ilkka

Attachment: Untitled.png (Downloaded 6 times)



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