Global Nav Open Menu Global Nav Close Menu; Apple; Shopping Bag +. Search Support. Currently dictionaries are not included in language packs, only in full installations. This limitation is a technical issue still to be fixed, see Bug 124473 for more details. Users who install language packs must take an extra step to manually download the matching dictionary from the Extensions website.
![]()
Summary: Identify installed languages, and add or remove Office 2016 language packs by modifying an existing installation or by deploying them as separate products.
You can add or remove language packs for an existing Office 2016 installation. This article describes the two methods that you can use to complete these tasks and how to view a list of the languages that are installed.
Important Atom 1.38 download mac installer.
This article describes methods of deploying and managing language packs for versions of Office 2016 that use the Windows Installer (MSI) installation technology, which are available for enterprises through volume licensing. If you have an Office subscription and you're deploying Microsoft 365 Apps, which uses the Click-to-Run installation technology, see Overview of deploying languages for Microsoft 365 Apps.
Overview
Office 2016 language packs enable Office applications to display menus, dialog boxes, Help topics, and other text in the user interface in multiple languages. Although the most frequently deployed languages for Office 2016 are released at the same time as the product is released, many other Office 2016 Language Packs are released over time. The Office 2016 Multi-Language Pack, which includes all available language packs, is not released until after all the individual language packs are released. However, if you upgrade your multilingual organization to Office 2016 before all the language packs are released, you can always add or remove additional languages at any time. The Office Multilanguage Pack and proofing tools for Office 2016 are available through Microsoft Volume Licensing programs. For more information, see Download language packs, language interface packs, and proofing tools for volume license versions of Office.
There are two methods that you can use to add languages after you deploy Office 2016:
Download Office Language Pack Mac Os
Note
Language-specific elements for Project 2016 and Visio 2016 are installed separately. You must rerun the Language Pack setup for these products. For more information, see Deploy language packs later in this article.
Before you begin
Determine which languages will be used at the beginning of your deployment. If you change users' configurations after the initial deployment and include additional languages as part of your customizations, you must first copy all the Office 2016 Language Packs that you want to deploy to the network installation point that contains the Office product files. For example, servershareOffice2016. A static list of the products that are contained in the installation source is built only during the initial creation of a customization .msp file. If you later add more languages to the installation source, the existing .msp file is not updated to reflect this change. Addressing this issue involves the following steps:
Failure to create and deploy a new .msp file might result in unexpected behavior, because the changes to an existing customization .msp file do not apply to the languages that are added. If you do not create a new .msp file and import the existing .msp file into that file, your deployment may test correctly in your lab. But users might not see the new language in their Office 2016 applications, or they might see only a subset of the language features. For more information, see To import a customization .msp file to add languages to an existing installation and Change users' configurations after installing Office 2013. (Although these articles are for earlier versions of Office, the information also applies to Office 2016.)
Mac Office 2011 Language Pack Download
For information about how to create a network installation point with multiple languages, see Customize language setup and settings for Office 2016.
Identify installed languages
You can view a list of languages that are installed for Office 2016 either during the initial installation or during a separate installation of a language pack at the following registry key, which displays the LCID for each enabled language:
HKCUSoftwareMicrosoftOffice16.0CommonLanguageResourcesEnabledLanguages
You can view the user interface (UI) language and fallback languages at the following registry key:
HKCUSoftwareMicrosoftOffice16.0CommonLanguageResources
Although all applications in the Office 2016 use a shared set of registry data to determine their UI language, they do not necessarily all appear in the same UI language. Applications in the Office 2016 usually appear with the UI language that is indicated in the UILanguage value of this registry key. But there are circumstances where this might not be the case. For example, some deployments might have Word 2016 and Excel 2016 installed in French, but another Office application that is installed in a different language. In this case, the other application examines the UIFallback list in this registry key, and uses the first language that works with its installed configuration.
To identify installed languages
Modify an existing installation
The recommended method for adding languages to an existing installation of Office 2016 is to run setup again and modify the existing Office installation. Because you are only modifying the original installation, no new entry appears in Add or Remove Programs in Control Panel.
You cannot replace the language of the shell user interface (Shell UI) that was installed during the initial installation. The Shell UI includes core elements of Office that register with the operating system, such as file name extensions, Tool Tips, and right-click menu items.
When you update a multilanguage installation, you can specify that the new language matches the user locale that is set on the local computer. For example, if your organization includes both English-speaking and Russian-speaking users, you might first deploy English to everyone. Later, when the Russian language pack becomes available, you can add the following line to Config.xml:
In this case, setup installs Russian language elements on any computer that has the user locale set to Russian. Users who have an English user locale are not affected.
To deploy additional languages after Office is installed
To deploy these languages for new Office 2016 installations, see Specify which languages to install and import existing customization .msp files into a new customization .msp file. A static list of the products contained in the installation source is built only during the initial creation of a customization file. If you later add more languages to the installation source, the existing customization file is not updated to reflect this change. For more information, see To import a customization .msp file to add languages to an existing installation. (Although this article is for an earlier version of Office, the information also applies to Office 2016.)
Deploy language packs
If you deployed multiple Office 2016 products in your organization and you must add more language support, you can deploy language packs as separate products. In this case, setup installs language-specific elements for every product in Office 2016. No matter which products users have installed, users can access the additional language versions.
For this deployment method to work, there must be at least one Office 2016 product installed on the computer that you are deploying to.
When you deploy language packs separately, you must consider the disk space that is required on users' computers. Language pack requirements range from 800MB to 1.5 GB of hard disk space that is needed.
Language-specific elements for Project 2016 and Visio 2016 are installed separately. In each language pack, the core product folder for Project 2016 is PMUI.ll-cc. The core product folder for Visio 2016 is VisMUI.ll-cc.
You must follow these steps for each language that you want to install.
To deploy language packs
To deploy these languages for new Office 2016 installations, see Specify which languages to install and import existing customization .msp files into a new customization .msp file. A static list of the products contained in the installation source is built only during the initial creation of a customization file. If you later add more languages to the installation source, the existing customization file is not updated to reflect this change. For more information, see To import a customization .msp file to add languages to an existing installation. (Although this article is for an earlier version of Office, the information also applies to Office 2016.)
Download Language Pack Microsoft Office 2011 MacRemove language packs
If the Office 2016 Language Packs were deployed as separate products, they can be removed by using Windows Add or Remove Programs.
Download Office Language Pack Mac Download
If the Office 2016 Language Packs were deployed with Office 2016 and not as separate products, the procedure to remove them resembles the deployment of the Language Packs. Instead of using the <AddLanguage> tag, use the <RemoveLanguage> tag.
You must follow these steps for each language that you want to remove.
Change Language Office MacTo remove language packsMicrosoft Office Mac Download
Related topicsComments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |