|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| migration question - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
drwho Member
|
migrating from ML6 i see that some translations of strings on buttons for example are completely different from the translation in the old ML file so i guess i made a mistake in the import process? any ideas?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
If translations are not at the right place it is nearly always related to missing or wrong .drc file. Please build you app incl. a fresh .drc file. Also build your translations using ML. Then create a new Sisulizer project and make sure it uses the same .drc file. The .drc file makes the link between the names in your app and numbers in your resources. If you make a new build in Delphi it may change the numbers. This is a limitation of Delphi and not Sisulizer. Without a fresh .drc the new numbering may not be linked correctly to the constant names. You should check in this direction. It is most probably the reason for what you see. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
drwho Member
|
in sisulizer itself i see another translation so i guess that is the problem i imported from the ML file BUT when ik scan the app it says the drc file is out of date (although it is generated today and with every build) does ML needs to be in sync with the same build before importing from ML? tia! marc
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
drwho Member
|
15:48:39 Warning DRC file is out of date. It may be dangerous to use it because resource strings may be mixed. i deleted the .drc file and did a full build after that i started the project and hit F5 so what does this mean?
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, There is not much more to say than the message says. Plese check under Project - Edit Source - <your source> the path of the .drc Sisulizer is using. Perhaps it points to some outdated version. Do the .drc and your exe listed in the setting have the same date and time stamp. That is what Sisulizer checks. My guess is that some old file is referenced. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
I agree with Markus, message could be result of mismatched files. migrating from ML6 i see that some translations of strings on buttons for example are completely different from the translation in the old ML file so i guess i made a mistake in the import process? Multilizer and Sisulizer are independent of each other tools and for this reason they aren't fully compatible. Multilizer and Sisulizer use different methods of context assigning (seem to me that Multilizer doesn't use DRC solution), so import based on context could give you incorrect results. Optionally, before import from Multilizer, you can check "Use index in list items" in "VCL options" tab of Delphi source properties dialog. It can improve import results. checking of this option requires re-scan of project. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
drwho Member
|
Markus.Kreisel wrote:Hi, for some reason my original reply vanished so i'll rewrite i deleted the drc file before the full build the project points to the right drc file after full build the timestamp is different from the drc file, 3-4 minutes so if those files should have the same timestamp, what could be the reason for this difference? anyway back to the import, should i first scan in ML on the same build and then perform the import OR should i build the resource and import the resource instead? what is the best way? but now to many strings are different from the translations in ML, so i wonder where those translated strings come from and what is odd, those strings are labeled 'complete' and in the import i set the imported strings to 'translated'
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
drwho Member
|
the only case in which i'm able to generate the same timestamp for both drc and exe is when i check the 'close on successfull compile' box so i guess d7 alters the timestamp if that form stays open for a while which makes the warning message a bit ackward
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
drwho Member
|
ok so i started a bit of experimenting this sunday noon and i found that - the import of ML was better if i scanned the exe after the build and before the import in Sisu, but it had its flaws although less of them - the import of the .FR file generated by ML was far better that the import of the ML project itself and i still don't know why i keep getting these drc out of date warnings, the files have the same timestamp (hh:mm) i don't remember getting these warnings with the previous version (running 312 now)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, I'll ask our CTO about this DRC issue. - the import of ML was better if i scanned the exe after the build and before the import in Sisu, but it had its flaws although less of them I think your ML project was created for old version of your source file, while Sisulizer project was created for newer version of source file. When you build project in ML, ML re-scan source and it update source in ML project. As result sources in ML and SL are matched. - the import of the .FR file generated by ML was far better that the import of the ML project itself As I mentioned in other post SL and ML aren't fully compatible and use different context method in their projects, so sometimes better solution is import from already localized files. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, The import from the .mlp is worse since the context it uses is different than the context Sisulizer uses. You could try the option to "Import by context first then by value" if you import from .mlp. Since the .mlp has language pairs this might close the gap of the missing translations. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
drwho Member
|
Markus.Kreisel wrote:Hi, my files are .mpr (ML6) anyway importing from the resource file was much better
|
||||||||||||||||
| |||||||||||||||||
| Current time is 05:32 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > migration question | |
Sisulizer software localization tool - Three simple steps to localize
