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
AlbelliCET
Member
 

Joined: Mon Apr 12th, 2021
Location:  
Posts: 3
Status: 
Offline
We have a Delphi application that is originally created about 15 years ago for the Dutch market. At this moment it is translated in 14 languages but the original language is still Dutch. Because it is hard to find Dutch speaking Delphi developers, we want to change the original language to English. A lot of text in the program is based on resource strings that come from one resource file, but there are also still a lot of strings that are hard coded in frm files.
I'm thinking about the following steps:
1. For every caption or text property in a frm file, find the corresponding english translation in the slp file (based on context) and replace the caption.
2. If there are other resourcestrings in form files, move them to the generic resource file.
3. Insert Dutch as a new language in Sisulizer and copy the original to the Dutch column.
4. Copy the English column to original and delete the English column.
Is this indeed the best way to do this or are there better suggestions?

jaska
Member
 

Joined: Thu Dec 7th, 2017
Location:  
Posts: 13
Status: 
Offline
Your method seems OK. However, it requires lots of manual work. Especially if you have a huge amount of forms, copy-pasting all string properties takes time and is error-prone.

What you could do is to take the English EXE or DLL created by Sisulizer. Then extract all the DFM resource data into .dfm files and use the covert.exe (part of Delphi) to convert them to a text-based .dfm file. Finally, replace the original .dfm files with these English .dfm files. Note that the DFM resource data inside the PE file contains a header. That needs to be removed because the binary .dfm files do not contain the header.

AlbelliCET
Member
 

Joined: Mon Apr 12th, 2021
Location:  
Posts: 3
Status: 
Offline
Thank you very much for your suggestion! I will have a look at this in a Proof of Concept!

AlbelliCET
Member
 

Joined: Mon Apr 12th, 2021
Location:  
Posts: 3
Status: 
Offline
By the way:
"For every caption or text property in a frm file, find the corresponding english translation in the slp file (based on context) and replace the caption" is supposed to become an automated process done by a tool we have to develop.....



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