- Write Greetings In 5 Registers
- English Register
- Microsoft Language Register Mac Download 2017
- Microsoft Language Register Mac Download 2017
- Microsoft Language Register Mac Download Free
Free downloads for building and running.NET apps on Linux, macOS, and Windows. Runtimes, SDKs, and developer packs for.NET Framework,.NET Core, and ASP.NET. Your Microsoft account comes with 5GB of storage and the option to add more when you need it. Find, lock, or erase a lost or stolen Windows 10 device, schedule a repair, and get support. Mixer is where gamers come together to play, celebrate, and share the best moments in gaming.
The following tables show the supported language packs for Windows 10 and Windows Server, and supported language interface packs (LIPs) for Windows 10. LIPs are available for Windows 10, but are not available for Windows Server. For more information, see Language packs.
The version of the language, LIP, or Feature on Demand must match the version number. For example, you can neither add a Windows 10 version 1809 LIP to Windows 10 version 1803 image, nor add a Windows Server 2019 language pack to Windows Server 2016.
You cannot add languages to Windows 10 Home Single Language and Windows 10 Home Country Specific editions.
To learn how to add languages to Windows, or where to get them, see Where to get language packs and LIPs.
For a complete list of supported languages and locales, see Locale Identifier Constants and Strings.
Supported Language Packs and Language Interface Packs
The following tables include these settings:
- Language/region- The name of the language that will be displayed in the UI. All 38 language packs are available for Windows 10 and Windows Server 2016. In Windows Server 2012 the user interface (UI) is localized only for the 18 languages listed in bold.
- Language/region tag- The language identifier based on the language tagging conventions of RFC 3066. This setting is used with the Deployment Image Servicing and Management (DISM) tool, or in an unattended answer file.
- Language/region ID- The hexadecimal representation of the language identifier. This setting is used with the keyboard identifier when specifying an input method using DISM.
- Language/region decimal identifier- The decimal representation of the language identifier. This setting is used in Oobe.xml.
Language Packs
| Language/region | Language/region tag | Language/region ID | Language/region decimal ID |
|---|---|---|---|
| Arabic (Saudi Arabia) | ar-SA | 0x0401 | 1025 |
| Bulgarian (Bulgaria) | bg-BG | 0x0402 | 1026 |
| Chinese (Hong Kong SAR) | zh-HK Note: No longer used. See zh-TW. | 0x0c04 | 3076 |
| Chinese (PRC) | zh-CN | 0x0804 | 2052 |
| Chinese (Taiwan) | zh-TW | 0x0404 | 1028 |
| Croatian (Croatia) | hr-HR | 0x041a | 1050 |
| Czech (Czech Republic) | cs-CZ | 0x0405 | 1029 |
| Danish (Denmark) | da-DK | 0x0406 | 1030 |
| Dutch (Netherlands) | nl-NL | 0x0413 | 1043 |
| English (United States) | en-US | 0x0409 | 1033 |
| English (United Kingdom) | en-GB | 0x0809 | 2057 |
| Estonian (Estonia) | et-EE | 0x0425 | 1061 |
| Finnish (Finland) | fi-FI | 0x040b | 1035 |
| French (Canada) | fr-CA | 0x0c0c | 3084 |
| French (France) | fr-FR | 0x040c | 1036 |
| German (Germany) | de-DE | 0x0407 | 1031 |
| Greek (Greece) | el-GR | 0x0408 | 1032 |
| Hebrew (Israel) | he-IL | 0x040d | 1037 |
| Hungarian (Hungary) | hu-HU | 0x040e | 1038 |
| Italian (Italy) | it-IT | 0x0410 | 1040 |
| Japanese (Japan) | ja-JP | 0x0411 | 1041 |
| Korean (Korea) | ko-KR | 0x0412 | 1042 |
| Latvian (Latvia) | lv-LV | 0x0426 | 1062 |
| Lithuanian (Lithuania) | lt-LT | 0x0427 | 1063 |
| Norwegian, Bokmål (Norway) | nb-NO | 0x0414 | 1044 |
| Polish (Poland) | pl-PL | 0x0415 | 1045 |
| Portuguese (Brazil) | pt-BR | 0x0416 | 1046 |
| Portuguese (Portugal) | pt-PT | 0x0816 | 2070 |
| Romanian (Romania) | ro-RO | 0x0418 | 1048 |
| Russian (Russia) | ru-RU | 0x0419 | 1049 |
| Serbian (Latin, Serbia) | sr-Latn-CS Note: No longer used. See sr-Latn-RS. | 0x081a | 2074 |
| Serbian (Latin, Serbia) | sr-Latn-RS | 0x241A | 9242 |
| Slovak (Slovakia) | sk-SK | 0x041b | 1051 |
| Slovenian (Slovenia) | sl-SI | 0x0424 | 1060 |
| Spanish (Mexico) | es-MX | 0x080a | 2058 |
| Spanish (Spain) | es-ES | 0x0c0a | 3082 |
| Swedish (Sweden) | sv-SE | 0x041d | 1053 |
| Thai (Thailand) | th-TH | 0x041e | 1054 |
| Turkish (Turkey) | tr-TR | 0x041f | 1055 |
| Ukrainian (Ukraine) | uk-UA | 0x0422 | 1058 |
Language interface packs (LIPs)
Except where noted, the following LIPs are available for Windows 10. For Windows Server, options to change keyboard and regional settings such as currency, time zones, and time/date format are available but LIPs are not available. For more information, see Language packs.
Note
As of Windows 10, version 1809, LIPs are are distributed as .appx files. To learn how to add an .appx, see Add languages to Windows.
| Language/region | Language/region tag | Base language/region | Language/region ID | Language/region decimal ID |
|---|---|---|---|---|
| Afrikaans (South Africa) | af-ZA | Primary: en-US Secondary: en-GB | 0x0436 | 1078 |
| Albanian (Albania) | sq-AL | Primary: en-US Secondary: en-GB | 0x041c | 1052 |
| Amharic (Ethiopia) | am-ET | Primary: en-US Secondary: en-GB | 0x045e | 1118 |
| Armenian (Armenia) | hy-AM | Primary: en-US Secondary: en-GB, ru-RU | 0x042b | 1067 |
| Assamese (India) | as-IN | Primary: en-US Secondary: en-GB | 0x044d | 1101 |
| Azerbaijan | az-Latn-AZ | Primary: en-US Secondary: en-GB, ru-RU | 0x042c | 1068 |
| Bangla (Bangladesh) | bn-BD | Primary: en-US Secondary: en-GB | 0x0845 | 2117 |
| Basque (Basque) | eu-ES | Primary: es-ES Secondary: en-GB, en-US, fr-FR | 0x042d | 1069 |
| Belarusian | be-BY | Primary: ru-RU Secondary: en-GB, en-US | 0x0423 | 1059 |
| Bangla (India) | bn-IN | Primary: en-US Secondary: en-GB | 0x0445 | 1093 |
| Bosnian (Latin) | bs-Latn-BA | Primary: en-US Secondary: en-GB, hr-HR, sr-Latn-RS | 0x141a | 5146 |
| Catalan | ca-ES | Primary: es-ES Secondary: en-GB, en-US, fr-FR | 0x0403 | 1027 |
| Central Kurdish | ku-ARAB-IQ | Primary: en-US Secondary: ar-SA, en-GB | 0x0492 | 1170 |
| Cherokee | chr-CHER-US | Primary: en-US Secondary: en-GB | 0x045c | 1116 |
| Dari | prs-AF | Primary: en-US Secondary: en-GB | 0x048c | 1164 |
| Filipino | fil-PH | Primary: en-US Secondary: en-GB | 0x0464 | 1124 |
| Galician | gl-ES | Primary: es-ES Secondary: en-GB, en-US | 0x0456 | 1110 |
| Georgian (Georgia) | ka-GE | Primary: en-US Secondary: en-GB, ru-RU | 0x0437 | 1079 |
| Gujarati (India) | gu-IN | Primary: en-US Secondary: en-GB | 0x0447 | 1095 |
| Hausa (Latin, Nigeria) | ha-Latn-NG | Primary: en-US Secondary: en-GB, fr-FR | 0x0468 | 1128 |
| Hindi (India) | hi-IN | Primary: en-US Secondary: en-GB | 0x0439 | 1081 |
| Icelandic (Iceland) | is-IS | Primary: en-US Secondary: en-GB | 0x040f | 1039 |
| Igbo (Nigeria) | ig-NG | Primary: en-US Secondary: en-GB | 0x0470 | 1136 |
| Indonesian (Indonesia) | id-ID | Primary: en-US Secondary: en-GB | 0x0421 | 1057 |
| Inuktitut (Latin, Canada) | iu-Latn-CA Not available in Windows 10. | Primary: en-US Secondary: en-GB | 0x085d | 2141 |
| Irish (Ireland) | ga-IE | Primary: en-US Secondary: en-GB | 0x083c | 2108 |
| isiXhosa (South Africa) | xh-ZA | Primary: en-US Secondary: en-GB | 0x0434 | 1076 |
| isiZulu (South Africa) | zu-ZA | Primary: en-US Secondary: en-GB | 0x0435 | 1077 |
| Kannada (India) | kn-IN | Primary: en-US Secondary: en-GB | 0x044b | 1099 |
| Kazakh (Kazakhstan) | kk-KZ | Primary: en-US Secondary: en-GB, ru-RU | 0x043f | 1087 |
| Khmer (Cambodia) | km-KH | Primary: en-US Secondary: en-GB | 0x0453 | 1107 |
| K'iche' (Guatemala) | quc-Latn-GT | Primary: es-MX Secondary: es-ES, en-US, en-GB | 0x0486 | 1158 |
| K'iche' (Guatemala) | qut-GT No longer used. | Primary: es-MX Secondary: es-ES, en-US, en-GB | 0x0486 | 1158 |
| Kinyarwanda | rw-RW | Primary: en-US Secondary: en-GB | 0x0487 | 1159 |
| Kiswahili (Kenya) | sw-KE | Primary: en-US Secondary: en-GB | 0x0441 | 1089 |
| Konkani (India) | kok-IN | Primary: en-US Secondary: en-GB | 0x0457 | 1111 |
| Kyrgyz (Kyrgyzstan) | ky-KG | Primary: ru-RU Secondary: en-GB, en-US | 0x0440 | 1088 |
| Lao (Laos) | lo-LA | Primary: en-US Secondary: en-GB | 0x0454 | 1108 |
| Luxembourgish (Luxembourg) | lb-LU | Primary: fr-FR Secondary: de-DE, en-GB, en-US | 0x046e | 1134 |
| Macedonian (FYROM) | mk-MK | Primary: en-US Secondary: en-GB | 0x042f | 1071 |
| Malay (Malaysia, Brunei, and Singapore) | ms-MY | Primary: en-US Secondary: en-GB | 0x043e | 1086 |
| Malayalam (India) | ml-IN | Primary: en-US Secondary: en-GB | 0x044c | 1100 |
| Maltese (Malta) | mt-MT | Primary: en-US Secondary: en-GB | 0x043a | 1082 |
| Maori (New Zealand) | mi-NZ | Primary: en-US Secondary: en-GB | 0x0481 | 1153 |
| Marathi (India) | mr-IN | Primary: en-US Secondary: en-GB | 0x044e | 1102 |
| Mongolian (Cyrillic) | mn-MN | Primary: en-US Secondary: en-GB, ru-RU | 0x0450 | 1104 |
| Nepali (Federal Democratic Republic of Nepal) | ne-NP | Primary: en-US Secondary: en-GB | 0x0461 | 1121 |
| Norwegian, Nynorsk (Norway) | nn-NO | Primary: nb-NO Secondary: en-GB, en-US | 0x0814 | 2068 |
| Odia (India) | or-IN | Primary: en-US Secondary: en-GB | 0x0448 | 1096 |
| Persian | fa-IR | Primary: en-US Secondary: en-GB | 0x0429 | 1065 |
| Punjabi (India) | pa-IN | Primary: en-US Secondary: en-GB | 0x0446 | 1094 |
| Punjabi (Arabic) | pa-Arab-PK | Primary: en-US Secondary: en-GB | 0x0846 | 2118 |
| Quechua (Peru) | quz-PE | Primary: es-MX Secondary: es-ES, en-GB, en-US | 0x0c6b | 3179 |
| Scottish Gaelic | gd-GB | Primary: en-US Secondary: en-GB | 0x0491 | 1169 |
| Serbian (Cyrillic, Bosnia and Herzegovina) | sr-Cyrl-BA | Primary: en-US Secondary: en-GB, sr-Latn-RS | 0x1C1A | 7194 |
| Serbian (Cyrillic, Serbia) | sr-Cyrl-CS Note: No longer used. See sr-Latn-RS. | Primary: sr-Latn-CS Secondary: en-GB, en-US | 0x0c1a | 3098 |
| Serbian (Cyrillic, Serbia) | sr-Cyrl-RS | Primary: sr-Latn-RS Secondary: en-GB, en-US | 0x281A | 10266 |
| Sesotho sa Leboa (South Africa) | nso-ZA | Primary: en-US Secondary: en-GB Microsoft cpu update. | 0x046c | 1132 |
| Setswana (South Africa) | tn-ZA | Primary: en-US Secondary: en-GB | 0x0432 | 1074 |
| Sindhi (Arabic) | sd-Arab-PK | Primary: en-US Secondary: en-GB | 0x0859 | 2137 |
| Sinhala (Sri Lanka) | si-LK | Primary: en-US Secondary: en-GB | 0x045b | 1115 |
| Tajik (Cyrillic) | tg-Cyrl-TJ | Primary: ru-RU Secondary: en-GB, en-US | 0x0428 | 1064 |
| Tamil (India) | ta-IN | Primary: en-US Secondary: en-GB | 0x0449 | 1097 |
| Tatar (Russia) | tt-RU | Primary: ru-RU Secondary: en-GB, en-US | 0x0444 | 1092 |
| Telugu (India) | te-IN | Primary: en-US Secondary: en-GB | 0x044a | 1098 |
| Tigrinya | ti-ET | Primary: en-US Secondary: en-GB | 0x0473 | 1139 |
| Turkmen | tk-TM | Primary: ru-RU Secondary: en-GB, en-US | 0x0442 | 1090 |
| Urdu | ur-PK | Primary: en-US Secondary: en-GB | 0x0420 | 1056 |
| Uyghur | ug-CN | Primary: zh-CN Secondary: en-GB, en-US | 0x0480 | 1152 |
| Uzbek (Latin) | uz-Latn-UZ | Primary: en-US Secondary: en-GB, ru-RU | 0x0443 | 1091 |
| Valencian | ca-ES-valencia | Primary: es-ES Secondary: en-GB, en-US | 0x0803 | 2051 |
| Vietnamese | vi-VN | Primary: en-US Secondary: en-GB | 0x042a | 1066 |
| Welsh (Great Britain) | cy-GB | Primary: en-US Secondary: en-GB | 0x0452 | 1106 |
| Wolof | wo-SN | Primary: fr-FR Secondary: en-GB, en-US | 0x0488 | 1160 |
| Yoruba (Nigeria) | yo-NG | Primary: en-US Secondary: en-GB | 0x046a | 1130 |
Write Greetings In 5 Registers
Related topics
-->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
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 Office 365 ProPlus, which uses the Click-to-Run installation technology, see Overview of deploying languages in Office 365 ProPlus.
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:
Modify an existing installation. When you use this recommended method, a language is treated as another feature to add to a deployment of Office 2016. This method involves combining the language resources with the source of the original installed Office 2016 product, changing the Config.xml file to add the appropriate languages, and rerunning Setup.exe from the Office 2016 installation source. This method installs only the necessary language parts for the products that are installed on the user's computer. For example, if you add Japanese to a basic installation of Office 2016 that does not include Visio 2016, the Visio 2016 resources for Japanese are not installed.
However, if the computer has both Office 2016 and Visio 2016 installed on it, you must add the Japanese resources for each product through two separate operations because there are two separate installation sources, one for Office 2016, and the other for Visio 2016.
Deploy language packs as separate products. This method involves running the language pack's setup file so that the full Language Pack is installed on the computer rather than modifying an existing installation of Office 2016. Deploying language packs is appropriate when you want to add languages after a deployment of Office 2016 but do not know which Office 2016 products are currently installed on users' computers. To use this method, you must have at least one Office 2016 product installed on the computer.
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:
Create a new customization file by using the Office Customization Tool (OCT).
Import your existing customization .msp file by using the File Import command in the OCT.
Make any additional customizations that you want and then save the .msp file.
After you update the installation source with additional languages, deploy the new .msp file to users.
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.)
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
English Register
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
Open the registry.
Expand the registry key HKEY_CURRENT_USERSoftwareMicrosoftOffice16.0CommonLanguageResourcesEnabledLanguages.
The LCID for the language is displayed. To identify the language, see Language identifiers.
To view the UI language, view the following registry key values and refer to Language identifiers.
HKEY_CURRENT_USERSoftwareMicrosoftOffice16.0CommonLanguageResourcesHelpLanguage
HKEY_CURRENT_USERSoftwareMicrosoftOffice16.0CommonLanguageResourcesUILanguage
To view the fallback languages, view the registry key value for HKEY_CURRENT_USERSoftwareMicrosoftOffice16.0CommonLanguageResourcesUIFallback. To identify the language, see Language identifiers and OptionState Id values in Office 2016.
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
Copy the files and folders in the new language packs from the source media to the original network installation point. When you are prompted to overwrite setup files, choose No.
Each language pack includes language-specific elements for every product in Office 2016. However, setup installs language-specific elements only for the Office product that you are updating.
In the core product folder for the product that you are updating, locate the Config.xml file.
For example, if you are adding languages to an installation of Office Professional Plus 2016, find the Config.xml file in the ProPlus.WW folder.
Open Config.xml in a text editor, such as Notepad.
Find the <AddLanguage> element. Uncomment the line by deleting the opening <!-- and closing --> tags.
Set the value of the Id attribute to the language tag that corresponds to the language that you want to install. You can specify more than one language by including additional <AddLanguage> elements and attributes.
For example, to add the Russian language pack, the line should resemble the following example:
If you add more than one language in Config.xml, you must specify one language as the language for the Shell UI. For example:
You must specify a ShellUI language, even though setup does not change the ShellUI language that was set for the initial installation.
Save the Config.xml file. Run Setup.exe and specify the path of your modified Config.xml file.
You must use a full qualified path. For example: servershareOffice2016setup.exe /config servershareOffice2016ProPlus.WWConfig.xml
where Office2016 is the root of the network installation point.
Because setup also recognizes language packs as separate products, make sure that you specify the Config.xml file for the Office product that you are updating, and not the language pack.
Microsoft Language Register Mac Download 2017
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
Copy all files and folders in the new language pack from the source media to a location on the network. If you are using an Office 2016 Multi-Language Pack, you can copy just the files and folders for the languages that you want to install. When you are prompted to overwrite setup files, choose No.
In the core product folder for the language pack that you are installing, locate the Config.xml file.
For example, if you are installing the Russian language pack, find the Config.xml file in the OMUI.ru-ru folder.
Run the language pack setup from the root of the network installation point for the Office 2016 Multi-Language Pack or Office 2016 Language Pack, and specify the path of the Config.xml file on the command line. For example:
servershareOffice2016LPSetup.exe /ConfigservershareOffice2016LPRUOMUI.ru-ruConfig.xml
where Office2016LP is the root of the network installation point for the language packs and RU is the language folder name.
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.)
Remove language packs
If the Office 2016 Language Packs were deployed as separate products, they can be removed by using Windows Add or Remove Programs.
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.
Microsoft Language Register Mac Download 2017
To remove language packs
If the language was deployed with the Office product (not as a separate product), locate the Config.xml file in the core product folder for the product that you are updating.
For example, if you are removing languages from an installation of Office Professional Plus 2016, find the Config.xml file in the ProPlus.WW folder.
Open Config.xml in a text editor, such as Notepad.
Find the <Display> element. Uncomment the line by deleting the opening <!-- and closing --> tags.
Set the value of the Level to 'basic' or 'none', CompletionNotice to 'yes', SuppressModal to 'yes', and AcceptEula to 'yes'.
The line should resemble the following example:
Find the <AddLanguage> element. If it is in the file, comment out the line by adding opening <!-- and closing --> tags around the element.
The line should resemble the following example:
Add the <RemoveLanguage> element.
Set the value of the Id attribute to the language tag that corresponds to the language that you want to remove.
For example, to remove the Russian language pack, the line should resemble the following example:
Save the Config.xml file.
If you edited the Config.xml file in the core product folder, run Setup.exe and specify the path of your modified Config.xml file.
You must use a fully qualified path. For example:
servershareOffice2016Setup.exe /ConfigservershareOffice2016ProPlus.WWConfig.xml
where Office2016 is the root of the network installation point.
Up arrow for mac microsoft word. From the View tab, now you can simply check a box to see a ruler or gridlines, or click the Arrange All button to stack various open Word documents atop each other. Although we sometimes mixed up the placement of commands within the Review and References tabs, those features were still easier to find than in Word 2003.Microsoft placed a lot of emphasis on the wow factor of Office's galleries of graphics, which share the Aero look of Windows Vista and are found throughout the Office applications.
servershareOffice2016LPSetup.exe /ConfigservershareOffice2016LPRUOMUI.ru-ruConfig.xml
where Office2016LP is the root of the network installation point for the language packs and RU is the language folder name.
You must complete the previous steps for each language that you want to remove.