|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Using resources.dll dynamically
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Using resources.dll dynamically
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Using resources.dll dynamically - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
DanMitsu Member
|
I am currently evaluating your software. I am a CSharp (Visual Studio 2005) and Java developer and I am using Sisulizer Professional version 1.6.13. After building the project, I have noticed that Sisulizer creates a folder inside the folder of my project and a dll called "myproject.resources.dll". What's the next step ? I mean, how can I load the resources from this dll ? I know how to do it with a .resx file but I do not know how to do it with this dll. It is important to say that I need a dynamic resource loading, I mean, the users of my applications can change language at run-time. Please, could you send me C# source code to do it ? Thanks in advance.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Renate.Reinartz Administrator 
|
Hi Dan, You can find a couple of sample files in \Net\CSharp under your Sisulizer installation directory. If you prefer to get a .resx file, which you compile, you can use the project or solution based localization. Just create a new project (File - New), and "Localize a file or files" in the Project Wizard. Just select your .Net project or solution file, and follow the wizard. I guess you used binary localization. In this case Sisulizer by default does not store the resX file because it is only temporary needed to create the assemblies. BTW: You can choose what Sisulizer creates by rightclicking the corresponding item in the project tree, and select Properties... In the Visual Studio .Net Properties dialog you specify the output on the File tab. You find more details in the online help. Just click the help button in the dialog. You are welcome Renate
____________________ http://www.sisulizer.de - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
DanMitsu Member
|
Thanks for your quick reply. Unfortunately, I still have several doubts. 1 - We are planning to make either binary localization as .resx localization in the same application. Will we be able to do it with Sisulizer ? 2 - In the Properties - File tab in Sisulizer, I only can select assembly output. Is this due to I have got evaluation version or professional version ? I mean, will we have got more output formats in the enterprise version ? 3 - I have tested the Net\CSharp\LangChange example. I only can select english language. Why ? I want to do the same by using resources in assemblies. Is this possible ? How ? Thanks in advance.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
>>1 - We are planning to make either binary localization as .resx localization in the same application. Will we be able to do it with Sisulizer ?<< Yes, you can always add more moduls, like e.g. EXEs, DLLs, XML, Databases, HTML, of your project with "Project - Add source". Each source can have its own format and has its own settings. But you can not use binary localization and source code localization on the very same source. >>2 - In the Properties - File tab in Sisulizer, I only can select assembly output. Is this due to I have got evaluation version or professional version ? I mean, will we have got more output formats in the enterprise version ?<< No the target selection depends on the actual source format. Some source formats may allow more output formats. Sisulizer only shows those making sense. >>3 - I have tested the NetCSharpLangChange example. I only can select english language. Why ? I want to do the same by using resources in assemblies. Is this possible ? How ?<< Have you first used "Project - Build all" in Sisulizer to create the assembly files the application needs to display more languages? The working result can be found in the Net\CSharp\LangChange\bin\Debug subdir after that. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
DanMitsu Member
|
Sorry, I did not create the assembly files. Now, I create them but I do not see japanese texts properly. Nevertheless, I see them properly in Sisulizer. Any suggestion ? >>Have you first used "Project - Build all" in Sisulizer to create the assembly files the >>application needs to display more languages? The working result can be found in >>the Net\CSharp\LangChange\bin\Debug subdir after that. Attachment: sisulizer_jap3.JPG (Downloaded 38 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, looks like you have not installed the Far East Language in Windows. Please read: http://www.sisulizer.com/support/codepages.shtml Sisulizer can emulate these for your convinience without the Far East Language option installed. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
DanMitsu Member
|
Hi, You told me 2 posts before that binary localization and .resx localization in the same application was not possible. Well, so I did it with no problem. I am a newbie CSharp programmer so maybe I did not explain the issue properly. Let's see : I have an application with Localization property equals to True. Besides, I have a .resx file with 1 string. I have traslated both (either UI components or the string from the .resx file) with Sisulizer. After doing that, I change language at runtime in my program. All the UI components are translated properly and a label which gets its text form the .resx file is also translated properly (VALOR_NL2 in the picture). So, it seems that it works. But ,my problem is : now, I want my .resx file to be refreshed from the translations made with Sisulizer. Is this possible ? Thank you in advance. Attachment: SISULIZER_JAP4.JPG (Downloaded 30 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Dan, if you use Project -> Build All doesn't Sisulizer create all the files needed for your localized version? I don't get the point why you want to have your ResX localized separately. Off course you can add more than one source in one SLP and share translations between them. You can even add your project as binary and as source code localization in one project but that would just mean that you localize the same things twice. The normal way would be to scan your .NET project file (File -> New), Sisulizer finds all strings, then you or your translator translates and if that is finished you use the build command (Project - Build All) to create the localized project ready to ship. It should be as simple as that. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
DanMitsu Member
|
Hi Markus, Yes, you are right. It is as simple as that. But, if I build my C# source code, the resources.dll files are created again, so translations made by the translator are lost. That's why I want his translations to be imported to the original .resx files. If I can do that, I will be able to build my C# source code and to have the new traslations "inside" the C# Sharp source code project. Do you understand my question ? Maybe there is another way of solving my problem and I am going in the wrong way. Thanks in advance.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Dan, I hope that can be solves also easily... After you build your new binaries (to the same path) you simply go into Sisulizer and use "Project -> Scan for Changes". Sisulizer re-scans your binaries, sees that they have been re-build since the last scan, re-uses all(!) existing translations and marks new and changed strings. Now you translate the new and changed strings (if any) and then you choose "Project - Build All" again. It is really that easy :-) You can also see a sample here: http://www.sisulizer.com/swf/sisulizer-scanforchanges.shtml You can even automatize this if you use the Sisulizer Enterprises command-line. You can add the SLMake commands to your build file. So if you build your software Sisulizer will also build your localized files. I really hope this solves your problem. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
... and more thing: the translations can never be stored in your original. Sisulizer never touches them. The translations are only stored in your .SLP which is used to create the translated version from your originals. Only this way Sisulizer can find out what is new and what has changed from build to build. This saves you a lot of money if your translator has only to handle new and changed strings. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 07:35 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Using resources.dll dynamically | |
Sisulizer software localization tool - Three simple steps to localize
