|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Newbie Questions - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Ed the C Member
|
Hi, i have been able to create a project from a resource only dll and create various language dlls and get them loaded and working in the program. I am using Visual Studio C++ 2005 under MFC. I used the dll directly into Sisulizer and produced each language dll (eg langFRA.dll). Then we load it at run time and then our menus, dialogs, etc are french - yay! I now wonder how best to proceed with dealing with resources in 3rd party dll's and controls. First is MFC itself. I have read the TN57 about how to do it, but am a bit confused. I am thinking the best way to handle it is to include the MFC resources into my resource dll. I am unsure of how exactly to do that since TN57 isn't clear enough for me. Worse, I do not want to have to be stuck building each language dll the way described in the TN57. Seems that would have to be done each version. Any help here would be great. (BTW, I found an earlier post referring to (http://www.sisulizer.com/online-help/MfcResourceDllFiles.htm) is no longer available?) Next - a 3rd party dll. We can open it with Sisuizer and translate, but i don't understand how to set the resource handles at run time as we do for the full application (we load the library and set the resources - eg load langFRA.dll and then AfxSetResourcehandle() Finally, what about Axtive-X controls? No really sure at what to do about those. Thanks for any links, help or advice in advance.
____________________ Ed |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Ed, Is there a reason why you don't scan your Visual Studio project and let Sisulizer find the pieces? Haven't you tried that? Perhaps that brings you closer to the target :-) Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, I tried to Google it without luck. What is TN57... since I'm not a C++ developer I'm stuck with that. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ed the C Member
|
sorry, forgot a 0 Technical note 57 = TN057 from MSDN http://msdn.microsoft.com/en-us/library/x6h91d9w%28VS.80%29.aspx Can you elaborate a bit on what you mean by scanning the project? Thanks.
____________________ Ed |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Ed, I mean, t you use File - New and then you give your main EXE file. If you need more files like DLLs you can use Project - Add Source. If you do this the EXE and the DLLs can share translations. If you later change one of the DLLs you simply use Project - Scan for Changes and Sisulizer re-uses existing translations. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator 
|
The easiest way is to compile a single EXE that includes all controls and all resources. Then scan that EXE with Sisulizer. Translate the resources. Finally you can choose to build single translated EXE-files or translated resource only DLL-files. Ilkka Attachment: cpp.PNG (Downloaded 18 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Ilkka.Salmenius Administrator
|
The main idea is to include as much as possible into the main EXE and localize it. If you are using 3-party DLL-files you have to translate then as well. If you build a localized EXE, then you have to build a corresponding localized DLL file for each localized EXE-files. If you are using localized DLL-files you have to load the right localized 3-party DLL-file dynamically. So you have add a little bit code. Same thing if you are using Multilingual EXE or Embedded resource DLL-files. Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 08:41 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 > Newbie Questions | |
Sisulizer software localization tool - Three simple steps to localize
