Fr mui rar
In the context of this tutorial, this package is necessary only if you will be customizing the application to run on Windows versions prior to Windows Vista. Download and install the package from its download site. As with the Windows SDK, if you are not installing the package to the default location, or if you are not installing on the system drive, which is usually the C drive, make note of the install path.
In most cases, this means that the application needs to carry and install the redistributable Nlsdl installer and not merely copy Nlsdl. This tutorial begins with the monolingual version of the Hello MUI application. The straightforward source code above makes the simplistic design choice of hard-coding, or embedding, all the output the user will see—in this case the text "Hello MUI". This choice limits the utility of the application for users who don't recognize the English word "Hello.
Microsoft Win32 has long exposed the capability for application developers to separate their UI resource data from application source code. This separation comes in the form of the Win32 resource model, in which strings, bitmaps, icons, messages and other items normally displayed to a user are packaged into a distinct section of the executable, separated from executable code.
But to help focus on the Win32 resource-related aspects, we leave the run-time DLL code stubbed out in dllmain. Subsequent sections of this tutorial make use of the HelloModule resource data being built here and also present appropriate runtime code. Examine dllmain.
If you view HelloModule. The one of greatest interest is the section that describes the "Hello" string:. This "Hello" string is the resource that needs to be localized that is, translated into every language that the application hopes to support. Create six more projects in the HelloMUI solution or as many of them as you wish to create six more resource DLLs for additional languages. Use the values in this table:. For more about. Using previous resource models, building any one of the seven HelloModule projects would result in seven separate DLLs.
Each DLL would contain a resource section with a single string localized into the appropriate language. Although appropriate for the historic Win32 resource model, this design does not take advantage of MUI. With the additional customization that is covered later in Step 5, applications can be enabled for multi-lingual support to run on versions prior to Windows Vista.
The primary mechanisms available to split resources from executable code, starting with Windows Vista, are:. See Resource Utilities for more information. For the sake of simplicity, this tutorial uses muirct.
This overview describes the required steps; the next section presents a command file that performs those steps. The command line above uses the configuration file DoReverseMuiLoc.
This type of configuration file is typically used by muirct. In this case, the DoReverseMuiLoc. For more information about how to prepare a resource configuration file, see Preparing a Resource Configuration File.
In addition to creating a HelloModule. In order to properly load at run-time the appropriate resources from the language-specific HelloModule. This is done by a command such as:. Similarly, muirct. However, in those cases the language-neutral DLL is discarded, as only the first one created will be needed. The commands that process the Spanish and French resources look like this:. One of the most important things to notice in the muirct. The value provided to muirct.
This language value is central and is used by muirct. An incorrect value produces resource loading failures for that particular. Each split. For this tutorial you create a command file containing the commands to split the various DLLs, and you invoke it manually. Note that in actual development work, you could reduce the potential for build errors by including these commands as pre-build or post-build events in the HelloMUI solution, but that is beyond the scope of this tutorial.
Copy DoReverseMuiLoc. When you create a release build, you copy the same DoReverseMuiLoc. The new run-time code presented in this step includes the module loading LoadLibraryEx and string retrieval LoadString logic. Build and run the application. The output will be displayed in the language currently set as the display language of the computer provided it is one of the seven languages we have built.
Although the previous example is able to display its output in different languages, it falls short in a number of areas. Perhaps the most noticeable is that the application is only available in a small subset of languages when compared to the Windows operating system itself. Of these options, the one providing an ultimate fallback language is highly advisable and is implemented in this tutorial by passing the -g flag to muirct.
This flag tells muirct. At run-time this parameter is used as a last resort to generate text to display to the user. In the event that an ultimate fallback language is not found and no appropriate resource is available in the language-neutral binary, loading of the resource fails. Therefore you should carefully determine the scenarios that your application might encounter and plan the ultimate fallback language accordingly. The other option of allowing for configurable language preferences and loading resources based on this user-defined hierarchy can greatly increase customer satisfaction.
Unfortunately, it also complicates the functionality needed within the application. Do take note that if too many additional language packs are installed, the disk space and system performance can be affected. In particular, disk space and system performance are affected during servicing operations, such as Service Pack installations, according to KB Windows Update will always display all language packs that are available. Any unwanted language packs can be made hidden in Windows Update.
To hide unwanted language packs in Windows Update, click on the Windows 7 Ultimate Language Packs category to highlight and hide all remaining language packs or click on and highlight individual language pack to hide language packs one by one in the Select the updates you want to install page, and then right-click the highlighted updates, and then select Hide update.
Arabic: windows6. After downloading the Windows 7 language packs, run the.
0コメント