Microsoft Office 2003 Multilingual User Interface Pack MUI 52
Garcia Miller
The Multilingual User Interface (MUI) is a Microsoft Office feature that gives the end user the ability to change the language of the user interface (UI). For example, an end user working with an English UI can change the language of the UI to Spanish.
Multilingual User Interface (MUI) is a technology that provides users a localized user interface for globalized applications and user interface language resource management in the Windows operating system. Support is provided for adding MUI functionality to globalized applications to run on Windows Vista and later, as well as many pre-Windows Vista operating systems. The MUI localization and resource management models enhance development, testing, and support for world-ready software.
The most visible benefit of MUI is that multiple users can share the same workstation and view the user interface in different languages. Corporations and OEMs will benefit from the capability they have to roll out, support, and maintain multilingual images with a single installation. But perhaps the main benefit of MUI comes in the efficiencies gained when developing, building and servicing your application. You can ship one core functionality binary applicable to all platforms, independent of UI language, which significantly reduces development and testing efforts. If you have to issue an update or a service pack, it will apply to all supported languages with no additional engineering effort. Later support for additional languages becomes a localization project instead of a full software development project.
This topic provides a conceptual overview of the Multilingual User Interface (MUI) technology, the platform support it provides for enabling multilingual user experiences, and the benefits it offers to the Windows ecosystem.
Once application source code is stored separately from the localized resources, it becomes easy to dynamically load the appropriate localized resources for a given application context based on a logic that takes into account system, user and application-level settings for the user interface language.
The level of support available for a multilingual user experience at the Windows operating system level and for multilingual application development on the Windows platform has evolved over time and across the different versions of Windows.
If you're an administrator who has deployed a volume licensed version of Office 2016 to your users, you can download an ISO image of the language packs, language interface packs, and proofing tools from the Volume Licensing Service Center (VLSC).
As a site owner or site collection administrator, you can use the Multiple Language User Interface (MUI) feature to offer individual users the ability to change the display language for their site user interface.
When you use a multilingual user interface and enable users to manually translate site elements in their preferred language, you can choose to overwrite their individual translations when a change is made to the same elements in the default language.
The core feature of MUI is the user-defined, system settings for preferred language that can be used/shared by all applications on a computer. The next most core feature is system functions (i.e. LoadString) that use this preference to load user interface assets at runtime from resources in the user's preferred language. To be MUI-enabled, an application need only store user interface assets as language-specific resources and use LoadStrIng to load them at runtime.
MUI also supports storing user interface assets as separate, single-language files which provides for development and deployment flexibility. This feature is optional. The resources can be stored in the application binary.
A localized version of Windows translates the base operating system, as well as all included programs [what programs?], including file and folder names [so it does localize file/folder names. this contradicts above], objects names [what's an object?], strings in registry [really? what strings?], and any other internal strings used by Windows into a particular language. Localized versions of Windows support upgrading from a previous localized version and user interface resources are completely localized, which is not the case for MUI versions of a product. [what is not the case for MUI?]
Windows Vista enhanced MUI technology to separate the English resources from the application logic binary files. The application logic files are now language-neutral a.k.a. language-independent. In other words, the application logic files are no longer English-centric. This separation allows for changing languages completely without changing the core binaries of Windows, and to have multiple languages installed using the same application logic binaries. Languages are applied as language packs containing the resources required to localize part of or the entire user interface in Windows Vista.
If your organization spans a diverse population, you may want to make content in your intranet sites available in more than one language. User interface elements like site navigation, site title, and site description can be shown in the user's preferred language. Additionally, you can provide pages and news posts on SharePoint sites that you translate and that are shown in the user's preferred language.
When the default and preferred language settings differ, SharePoint will allow users to edit site content in their preferred language without enabling multilingual features. Additional language information is provided when editors make changes to navigational labels, site descriptions, footers, and the site's name to prevent users from editing site content into the wrong language.
In the image above, the site's default language is French, and the user's preferred language is English. If the user edits this navigational node, it should be in the French language to prevent displaying a label in English when the site's default language is French. If the user wants to edit this navigational node into English, they should enable the multilingual feature.
During installation, files that enable users to change the language of the user interface and online Help are copied to the destination hard disk. Localized templates and wizards are also added to the appropriate Office 2003 applications.
MUI packs for a certain product perform the same task as localized versions of the product, but with some key technical differences. While both localized versions of software and MUI versions display menus and dialogs in the targeted language, only localized versions have translated file and folder names. A localized version of Windows translates the base operating system, as well as all included programs, including file and folder names, objects names, strings in the registry, and any other internal strings used by Windows into a particular language. Localized versions of Windows support upgrading from a previous localized version and user interface resources are completely localized, which is not the case for MUI versions of a product. MUI versions of a product do not contain translated administrative functions such as registry entries and items in Microsoft Management Console.
The MUI architecture separates the language resources for the user interface from the binary code of the operating system. This makes it possible to change languages completely without changing the core of Windows. Languages are applied as "language packs" containing the resources needed to localize any part of the user interface in Windows.
Language Packs, also known as Language Interface Packs (LIPs), are additional language resources that can be downloaded and installed on top of a base Microsoft software installation. These packs contain localized user interface elements, such as menus, dialog boxes and help documentation, to allow users to interact with the software in their preferred language. Usually, Language Interface Packs do not provide a full multilingual user interface but offer around 80% translated and localized user experience.
LIPs are partial language packs that translate only the essential elements of the user interface, such as the main menus and dialog boxes. They are suitable for users who need basic language support but prefer to use the software in the default language.
Full language packs, as the name suggests, offer comprehensive language support for your Microsoft software. They translate not only the main user interface but also additional features, help files, and more. Full Language Packs enable you to use the Microsoft Software entirely in your preferred language.
Microsoft Office language packs allow users to change the interface language of Office applications. This means that you can use Office menus, buttons, options, and commands in your preferred language. Although the available languages may vary depending on the Office version, you can find language packs for less common European languages, such as Luxembourgish, Catalan and Czech for example.
In principle you can use one Microsoft software license with different Language Packs. Language Packs do not affect the software license or its functionality, as language packs only provide language options for the user interface.
Changing the language in Microsoft Word can be a great advantage. It permits users to produce documents in different languages, for a global audience. And it also allows bilingual and multilingual people to effortlessly switch between languages, without external translation tools.
We all use a minimum of one operating system language on our computers. It may be likely that a company that has many employees may end up with several nationalities. This means, more multilingual user interface (MUI) pack is required in your operating system deployment. When a MUI Pack is installed, the user interface language can be change to one of 33 supported languages.
The Designer for WiX Toolset lets you forget the plain Windows Installer XML and concentrate on your deployment logic. It integrates several editors with the Visual Studio IDE and provides a set of vdproj designers to configure the file system, registry, user interface, custom actions, launch conditions and more for your setup projects.
e2b47a7662