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
Albeit excluded slmake adds component to slp file - 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: Tue Feb 6th, 2018 09:48 am
PM Private Upload Quote Reply
DelphiDev
Member
 

Joined: Mon Jan 21st, 2013
Location:  
Posts: 12
Status: 
Offline
Hi Sisulizer Team,

Trying to reduce the size of our translation project (currently ~ 18MB), I began to remove unneeded XML nodes from the document and created excluded components for the unneeded classes. (Tools -> Platforms -> VCL -> Components, I added TWindowsVersionFolder (and some more) and on Options tab I set the Component to "Enabled" and also checked "Exclude the whole component and its properties" and "Exclude all string properties by default".

After a build with slmake however, the components are back in the slp file.

What am I doing wrong here?

We're using Sisulizer 3.44.

Thanks

Greg

Last edited on Tue Feb 6th, 2018 10:13 am by DelphiDev

Back To Top PM Private Upload Quote Reply

 Posted: Tue Feb 6th, 2018 02:42 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3128
Status: 
Offline
To exclude resources from scanning you need to filter them out using the options in Project - Edit Source - <your source> - Resources.

Here you can exclude resource blocks. Sisulizer needs the original resource structure as a blue print to build new resources.

If you simply delete parts in the editor the next Project - Scan for Changes will find them again (if not excluded by the rules in the source settings).  If you build your project Sisulizer first makes it up-to-date = finds new strings not in the project etc.
There are filter to hide strings from seen in the editor. But this does not lower the memory impact.
Hope this helps
Markus



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

Current time is 10:36 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 > Albeit excluded slmake adds component to slp file



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