I am working on this localization project for an app.
All of our English strings are in LocalizationResources.resx. Now we are trying to support for Japanese. We now include the Japanese version of resx i:e LocalizationResources.ja-JP.resx to the same location/solution project where english resx resides.
According to Microsoft there is no code change needed because .NET is smart enough to pick the correct resx file based on the current system locale.
When we run the app from Visual studio in Japanese locale, the app launches in Japanese. Thats good...
When we run the app by running an exe (generated by building the solution) in Japanese locale, the app launches in Japanese. Thats good as well...
BUT when we build solution to generate an MSI, then install it in Japanese locale, then launch the App it shows up in English!!! Clearly the visual studio and the exe know to read from Japanese resx but why doesnt the app(installed by MSI) run in Japanese???
I tried several combinations of settings for the resx file, such as "Build Action" = "Embedded resources", and "Copy to output directory" = Copy always/copy if new/do not copy.
I know for the fact that our packing tools do not differentiate or exclude any file from being part of MSI. So how to resolve this?
Related
While in C# it's pretty easy, in Delphi it seems that it's not. I have this test project in french:
And I have added italian and english as languages in this part of the IDE following the steps:
I've followed the steps I've found in the doc about resource dlls. Now I have this
But now, how do I translate the caption of the buttons? I haven't found useful info in the documentation, it seemed pretty confusing to me.
I have done the following with ITA
And ENG
But in Project > Languages I set ITALIAN as active but still I see everything in english. Am I missing something?
I already know that there are localization tools like TsiLang, TLanguages, DKLang and so (I already rely on them) but I wanted to try this built in feature.
All you need to do is to compile and build the whole group not just the project, you can find this under:
Project > Compile All Projects
Project > Build All Projects
Then run your project again, it should run the language you have been set as Active
In the document Support Statement for Visual Basic 6.0 on Windows... it states:
Localization Support Binaries
The following binaries are necessary for supporting Visual Basic 6.0
applications running on localized versions of the Windows operating
system. They are supported but are not shipped in Windows. These files
are required to be shipped with your application setup.
That seems pretty clear in itself.
For instance, mfc42jpn.dll is required for Japan, mfc42ita.dll for Italy, etc.
However, I cannot find any source of these files from Microsoft. Where can they be sourced?
Note - there are some random DLL download websites which turn up the correct filenames, but I'd far prefer an authoritative source.
You should apply SP6. According to this, it covers all English versions of these products, as well as all localized versions.
On the VB6 installation CD those files can be found in the \OS\SYSTEM folder.
For the OP's given example of MFC42.dll it includes:
MFC42.DLL
MFC42CHS.DLL
MFC42CHT.DLL
MFC42DEU.DLL
MFC42ENU.DLL
MFC42ESP.DLL
MFC42FRA.DLL
MFC42ITA.DLL
MFC42JPN.DLL
MFC42KOR.DLL
I keep my system locale as English and changed the Format to German, but the Wix installation process changed to German! How can I keep the Wix installation language as English (as the system locale)?
I believe you want to specify just the en-us culture when building
For Example
light.exe myinstaller.wixobj -cultures:en-us -ext WixUIExtension -out myinstaller-en-us.msi
See here for more information as well as how to specify the culture in Visual Studio
I'm realizing a custom setup for my outlook addin. I want the installer in Dutch language, but VS 2010 doesn't support this language.
Is there a solution to my issue?
The default procedure to make a dutch language msi setup is to use orca.exe on the msi file and translate the TEXT column of some tables. (you can also do this by extracting the msi database and by importing it back in the msi when the translation has been done).
But there is the other way: Creating the language support directly in the Setup project creator.
I'm using VS.NET 2003 (yeps still the old version) and when you create a setup project you have no dutch language support in the project localisation. I figured out how that thing works but I'm stuck in the language change of the msiloadr.bin and the webloadr.bin files (both dll files included in the distribution) (step 3 in the comment below). The unusual procedure to include directly the language support in the VS.Net Setup project :
1) get the local identifier and the code page for your language (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/nls_238z.asp)
2) Go to the VS.NET/Common7/Tools/Deployment/VsdDialogs directory and copy 1033 (english) directory to 1043 directory (dutch). Translate all the files in that directory with orca.exe and update the 1033 language code to 1043
3) Go to the VS.NET/Common7/Tools/Deployment/MsiRedist directory and copy 1033 (english) directory to 1043 directory (dutch). Here we need to update the bin files (DLL) to set it up as a dutch language.
4) Update the registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.1\Deployment\DialogTemplates:)
Append ", Dutch" to the Languages key
Append ", 1043" to the Identifiers key
Append ", 1252" to the CodePages key
Once you have done that you'll be able to compile any Setup project in the dutch language and this can be done for all the missing languages. (If you solve the 3rd step)
Maybe you have some solution to solve for the unofficial sulution by tweaking VS.NET :-)
Copied from: http://social.technet.microsoft.com/Forums/windows/en-US/2d062f34-5615-47c8-aa7b-a69fbd68e983/how-to-make-a-installer-in-dutch-language
Please read this :-
Set up creation using selected language
I have a Windows Installer XML (WiX 3.5) project and five localization files for my installer. Therefore WiX creates five .msi files, for every language one. How can i put all in one .msi and let the user select the language when executing the installer?
I heard something about a bootstrapper, but then i would have a Setup.exe and i need a msi file. Is it not possible to adabt the localization strings after compiling with WiX?
This can be done using transforms. Please take a look at this article:
http://www.installsite.org/pages/en/msi/articles/embeddedlang/
There are 2 parts to making this happen,
localisation of the Installer UI, and/or
choice of installed files.
The method I chose will automatically select the local (or near local) language, and can also be forced to a specific transform using command line options. This doesn't prompt the user to choose which language to install in - so maybe it doesn't actually meet your needs.
The second 'installed files' doesn't seem to be documented as well and I was recently asking about it in Why would MST not include files with different content.
As a response provided there is now an ANT build script using Windows7 SDK & antdotnet