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
Multilingual exe - 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: Mon Oct 2nd, 2017 01:10 pm
PM Private Upload Quote Reply
drwho
Member
 

Joined: Fri Feb 8th, 2008
Location:  
Posts: 104
Status: 
Offline
hi, since we have major slowdown using D10 and resource dll's on windows XP (yes i know XP is no longer supported but i have stubborn clients)
i was looking into the multilingual option
but is there a way to force a language using this option?
if so how would i do this?

(any other solution is better then shipping multiple exe's with embedded translation)

tia,
Marc

Back To Top PM Private Upload Quote Reply

 Posted: Mon Oct 2nd, 2017 01:43 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

The problem with multilingual ressources is, that Windows, and only Windows, chooses the language at startup. Thats why a great option is not used often in the wild.

Have you tried the option with external languages DLLs not compiled into the binary? Perhaps is the extraction of the dll the bottle neck under XP?

Do you know our manual for VCL users?

https://www.sisulizer.com/translation/vcl/VCL.pdf

Markus



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

 Posted: Mon Oct 2nd, 2017 01:55 pm
PM Private Upload Quote Reply
drwho
Member
 

Joined: Fri Feb 8th, 2008
Location:  
Posts: 104
Status: 
Offline
it's not the extraction of the dll's itself that takes time, that is only at startup, it's during runtime when new functions are used (all forms are created on the fly)
...
and i'm talking of differences of 15 seconds in certain areas...

Back To Top PM Private Upload Quote Reply

 Posted: Mon Oct 2nd, 2017 02:03 pm
PM Private Upload Quote Reply
drwho
Member
 

Joined: Fri Feb 8th, 2008
Location:  
Posts: 104
Status: 
Offline
is there a structural difference in the vcl using resource dll's instead of baked in translations (which are also resources?)
just trying to pinpoint the core of the problem
no problem running in W10

Back To Top PM Private Upload Quote Reply

 Posted: Fri Oct 6th, 2017 03:02 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1979
Status: 
Offline
No there is. Internally in VCL there is a resource handle. That handle can point to the resource block of the main EXE or LIB but can also point to a resource DLL. There is no speed difference.

Could it be that you change the language after each form has created. I mean when form is initially created it will use the default resource handle but then then us use Sisulizer's code to translate the form into another languages. Sisulizer's runtime language change is very fast but there might be some problem on certain property.

Ilkka



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

Current time is 04:28 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Multilingual exe



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