|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Wrong string result - Bugs and Quirks in Sisulizer - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
bikemike Member
|
Hi folks, If Sisulizer returns the untranslated value for the wrong resource where do I start to fix or even understand this? Using Sisu 1.6.21 with Delphi 7 We are using resource.dll localization. Say I have two strings that are untranslated SFred = 'Freddy'; SBob = 'Bobby'; Say they are in different units I have rescanned the project and built the items... Building "mypath\myexe.FR", the French resource file of "mypath\myexe.exe" ...before running the application. Say at run time in English I see 'Freddy' where the string SFred is used. All good! Say I switch to French at runtime and I see 'Bobby' where I should see 'Freddy' That's pretty much what seems to be happening. Thoughts?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Remember that every time you compile a Delphi application after you have changed the source code it might be that Delphi assing new ids for resource strings. If you run application after rebuild and application has resource DLLs that still have the old resource ids VCL is loading wrong strings. String loading is always done using resource ids (that are integer assigned to string on compile time) and not by resourcename (that are string name assinged by developer e.g. SMyString = "...") This is why it is very important that resource DLL are in synch with the EXE. If you recompile EXE use Sisulizer to rebuild the resource DLLs. If the output file of Sisulizer project is not the same dir as EXE make sure that you copy the created DLLs to the same directory as EXE. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
bikemike Member
|
Per my post, I beleive I have been doing exactly that. I will recheck the process shortly and confirm the results or eat my hat - and reply again....
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
Can you send me the original EXE and one localized DLL. Tell me also what is the string in the EXE that translates wrong. I will check the files. support (at) sisulizer.fi Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
One more question. Are you using resource DLL as separate files (e.g. Project1.exe, Project1.DE, Project1.FR, ..) or are you embedding the resource DLLs to the EXE. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
bikemike Member
|
We have multiple resource dlls When I religiously build / scan / build / execute all seems well today. I tried a few things:
I will assume now then that something I was doing in Delphi was causing a rebuild that I was not aware of and this was causing the missalignment of the resource ID's. Thanks for you time.
|
|||||||||||||
| ||||||||||||||
| Current time is 04: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) > Bugs and Quirks in Sisulizer > Wrong string result | |
Sisulizer software localization tool - Three simple steps to localize
