|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Scan for changes - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... | ||||||||||||||
| Author | Post | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
techotel Member
|
Hi. When we hit the "Scan for changes"-button, Sisulizer sometimes makes misplaced some of the translation. Prehaps it has something to do with this forum-thread: http://forum.sisulizer.com/view_topic.php?id=660&forum_id=3&jump_to=3567#p3567 If we dont hit the button (Scan for changes), and just build, then sisulizer will automic find out that the exe-file has changes, and more string have been added. And it will handle them correct. It we hit the button (Scan for changes), and saves the project, then the next time we open the project, some of the strings have been moved arround... I mind, that the paths (DRC and DRP) of the project messed up, when moving from one computer to another, where these path doesnt exist. Prehaps the problems is related to that, when scanning for chages... (if it use the path given for DRP and DRC), when they are incorrct, when scanning for change. Hope this sound more clear than it looks... Martin
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Martin, Delphi may change the context with every build. So it is absolutely nessessary that the project links to the matching .drc. You need the .drc made by the compiler/linker while he created the binary. Only with the proper file the context will be correct. Please check that your project references the matching .drc. You find that if you right click your source in the project tree and choose properties. If in doubt compile your Delphi project to get a matching set of files. While building your project Sisulizer reads your binary as a sort of a template for the target. It sees that something was changed but it does not freshen (Scan for Changes...) the .slp. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
techotel Member
|
In other words... Computers that don't have a corresponding exefil, DRC and DRP file, should not "Scan for Chages". Correct?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator 
|
DRC file should alway be used. The only exception is that if you are 100% sure the original EXE won't be recompiled after changing source code. DPR is only needed if you use _ character in the file name of the forms that contain resourcestring. Safest way is to always specify both DRC and DPR. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Ilkka.Salmenius Administrator 
|
I think that your problems are related to this http://forum.sisulizer.com/view_topic.php?id=660&forum_id=3&jump_to=3567#p3567 As you also guessed. Please wait the build 1.6.20. That has been fixed in it. best regards Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 07:58 pm | |
| Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Scan for changes | |
Sisulizer software localization tool - Three simple steps to localize
