Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.microsoft.com/en-us/deployoffice/overview-deploying-languages-microsoft-365-apps below:

Overview of deploying languages for Microsoft 365 Apps - Microsoft 365 Apps

This article covers the options for deploying languages for Microsoft 365 Apps, including what method to use, where to deploy languages from, how to deploy proofing tools, and best practices. We recommend using this article as part of planning your Office deployment.

The guidance in this article applies to the following Office products:

• Microsoft 365 Apps for enterprise, which comes with many Office 365 and Microsoft 365 enterprise plans.
• Microsoft 365 Apps for business, which comes with some Microsoft 365 business plans.
• The subscription version of the Project desktop app that comes with Planner and Project Plan 3 or Planner and Project Plan 5.
• The subscription version of the Visio desktop app that comes with Visio Plan 2.

You can't use language resources for Windows Installer (MSI) versions of Office with Microsoft 365 Apps, which uses Click-to-Run. For example, you can't use language packs downloaded from the Volume Licensing Service Center (VLSC) with Microsoft 365 Apps.

In general, you deploy languages for Microsoft 365 Apps with the same process and tools that you use to deploy Office itself. You can deploy multiple languages by including those languages directly in the Office packages, or you can deploy languages as a separate package, after Office is already installed. The steps in this article assume that you're deploying with Configuration Manager or the Office Deployment Tool, and that you use the Office Customization Tool (OCT) to create the configuration files for your deployment. If a setting isn't yet available in the OCT, steps are given for creating the configuration file in a text editor.

When deploying multiple languages in a large organization, we recommend these best practices:

• Automatically install the same languages as the operating system.
• If you deploy Office from a local source on your network, use the Office Content Delivery Network (CDN) as a backup source for language packs that might not be available at that local source.
• When adding languages to an existing deployment of Office, you can deploy just the language packs, rather than the full version of Office.
• If you upgrade from a Windows Installer (MSI) version of Office, you can automatically install the same languages as a previous MSI installation.
• When building Office packages to deploy, include all the language packs you plan to deploy in each package. Creating separate packages for different language sets can make the Office deployment difficult to manage.
• If you deploy a subscription version of the Project or Visio desktop app on a device with Office already installed, you can automatically deploy them in the same languages as the installed version of Office.
• If you use some languages only as editing tools, you can deploy just the proofing tools instead of full language packs to conserve network bandwidth.

This article also includes the list of supported languages and details on how Office conserves network bandwidth when downloading language packs for deployment.

If your organization allows it, users can install Microsoft 365 Apps languages directly from the Office 365 portal. When users install Office from the Software page, they select a language from the Language drop-down box. If a user needs another language, they can just rerun the process for each required language. The setup adds the selected language to the user's device.

To deploy Microsoft 365 Apps in multiple languages, you need to include the other languages in the Office packages you create. To do so, select the languages you want to deploy in the Language section when creating the configuration file in the Office Customization Tool.

If you deploy Office from a local source on your network, you must download your languages to that source, in the same way that you download the Office package. For more information, see Download the installation files for Microsoft 365 Apps. When deploying from a local source, we recommend that you use the Office Content Delivery Network (CDN) as a backup source for language packs.

For more information on standard deployments, see Plan your enterprise deployment of Microsoft 365 Apps.

When you select a primary language in the Office Customization Tool, it sets the language for displaying shortcuts, right-click context menus, and tooltips, known as the Shell UI language. To change the Shell UI language after installing Office, you need to uninstall and then reinstall Office.

After deploying Microsoft 365 Apps, you can deploy more languages for Office. To do so, use the same process and tools you used to deploy Office, such as Configuration Manager or the Office Deployment Tool.

1. If you're deploying languages from a local source, make sure the languages are available at that source. For more information, see Download the installation files for Microsoft 365 Apps.
2. If you use a local source, we recommend that you use the Office Content Delivery Network (CDN) as a backup source for language packs.
3. When creating the configuration file in the Office Customization Tool, select Language Pack as the Additional Product in the Products section.
4. In the Language section, select the other languages you want to install.
5. Deploy the languages using the same process you use to deploy Office.

When you add to an existing deployment, the ODT can automatically detect the architecture (32-bit or 64-bit) and source location (Office CDN or local source) used by the current Microsoft 365 Apps installation. This means you don't have to specify these values when creating the configuration file. As a result, a single configuration file can serve multiple deployment groups. However, when using the Office Customization Tool, you must specify all these values. Therefore, this feature is available only if you create the configuration file using a text editor.

Users need local administrator permissions on their devices to install other languages for Office by default. However, to enable users without local admin rights to install a new language, activate the policy setting 'Allow users who aren't admins to install language accessory packs.'

You can use either Group Policy or Cloud Policy to enable the policy setting. In the Group Policy Management tool, you can find the policy setting under User Configuration\Policies\Administrative Templates\Microsoft Office 2016\Language Preferences\Display Language.

The policy setting applies to Word, Excel, PowerPoint, Outlook, and OneNote. Users can install another language by going to File > Options > Language > Office display language > Add a Language... in their Office app.

Note

• This feature isn't available when you enable programmatic control of Microsoft 365 Apps updates. For example, you enable programmatic control when you use Configuration Manager to deploy Microsoft 365 Apps.

If you're using a local source to deploy Office, we recommend that you use the AllowCdnFallback attribute in your configuration.xml file. This attribute enables you to use the Office CDN on the internet as a backup source location for the language files if they aren't available on your local source. For more information, see Use the Office CDN as a backup source for language packs.

Note

If you enable the "Delay downloading and installing updates for Office" policy setting, user installations of languages are also delayed by the number of days specified in the policy setting.

Each language version of Microsoft 365 Apps includes proofing tools for a set of companion languages. For example, when you deploy the English version of Office, users receive proofing tools for English, Spanish, and French. These proofing tools include spelling and grammar checkers, thesauruses, and hyphenators. They might also include language-specific editing features such as Language AutoDetect, AutoSummarize, and Intelligent AutoCorrect.

If you want to deploy proofing tools in other languages beyond the companion languages, you can deploy the full language pack for that language or you can deploy just the proofing tools for that language. Many administrators choose to deploy just the proofing tools to conserve bandwidth on the network and speed up installation on client computers.

To deploy just the proofing tools, use the same tools you used to deploy Office, such as Configuration Manager or the ODT. You can include proofing tools in the initial deployment of Office, or you can add them later to an existing deployment.

Note

To install proofing tools, you must be using at least Version 1803 of Microsoft 365 Apps. You must also be using the latest version of the Office Deployment Tool, which you can download from the Microsoft Download Center. In addition, you can't use the Office Customization Tool to create the configuration file, because this feature isn't yet available in that tool. Instead, you must edit the configuration file in a text editor.

If you're adding to an existing deployment, the ODT automatically uses the same architecture (32 bit or 64 bit) and source location (Office CDN or local source) as the existing installation of Microsoft 365 Apps. Because the same architecture and location is used, you don't need to specify these values when creating the configuration file, meaning you can use a single configuration file to deploy to multiple deployment groups.

1. When creating the configuration file in a text editor, use "ProofingTools" as the Product ID, along with the appropriate Language IDs, as shown in the example.
2. When deploying languages from a local source, you must download the proofing tools to that source first. For more information, see Download the installation files for Microsoft 365 Apps.
3. When you use a local source, include the AllowCdnFallback attribute in the configuration file to use the Office CDN as a backup for language packs and proofing tools, as shown in the example.

For details on how to edit the configuration file in a text editor, see Configuration options for the Office Deployment Tool.

This configuration file installs proofing tools for German and Italian using Monthly Enterprise Channel on a device with Office already installed. If the original installation of Office was from a local source, make sure to download the proofing tools to that source. If the tools aren't found at the local source, the AllowCdnFallback setting installs the tools directly from the Office CDN.

<Configuration>
  <Add Channel="MonthlyEnterprise" AllowCdnFallback="TRUE">
    <Product ID="ProofingTools">
      <Language ID="de-de" />
      <Language ID="it-it" />
    </Product>
  </Add>
</Configuration>

When you deploy Office, automatically install the same languages used by the operating system. Include these steps in your standard Office deployment process and tools:

1. When creating the configuration file in the Office Customization Tool, select Match Operating System as the primary language.
2. If you use a local source, we recommend that you use the Office CDN as a backup source for language packs. To do so, select Fallback to the CDN for missing languages in the Installation section.

When Match Operating System is used, the base language of the operating system and all active display languages for user profiles on the device are installed. Match Operating System can be used in combination with a fixed list of languages.

You can automatically deploy Visio and Project in the languages that are in use by an existing version of Microsoft 365 Apps. To do so, use the same process and tools you used to deploy Office, such as Configuration Manager or the Office Deployment Tool.

Note

You can't use the Office Customization Tool to create the configuration file, because this feature isn't yet available in that tool. Instead, you must edit the configuration file in a text editor.

If you're adding to an existing deployment, the ODT automatically uses the same architecture (32 bit or 64 bit) and source location (Office CDN or local source) as the existing installation of Microsoft 365 Apps. Because the architecture and source location are the same, there's no need to specify these values when creating the configuration file. Using the same location allows you to use a single configuration file for deploying to multiple deployment groups.

1. When creating the configuration file in a text editor, use "MatchInstalled" as the Language ID, as shown in the example provided.
2. Optionally, you can add the TargetProduct attribute to the Language element. Adding this attribute lets you choose which Office product defines the languages for installation. For example, setting TargetProduct to "O365ProPlusRetail" installs Office products in the same languages as Microsoft 365 Apps for enterprise on the client computer, if installed. If you want to match all installed languages, you can specify TargetProduct="All".
3. When deploy languages from a local source, you must download any possible matched languages to that source first. For more information, see Download the installation files for Microsoft 365 Apps. You can't use the /download switch for ODT on a configuration file that contains the MatchInstalled keyword. You have to use a separate configuration file.

You can also use MatchInstalled as the Language ID when adding Office apps to or removing them from an existing installation of Office.

For details on how to edit the configuration file in a text editor, see Configuration options for the Office Deployment Tool.

<Configuration>
 <Add Channel="MonthlyEnterprise" AllowCdnFallback="True"> 
  <Product ID="VisioProRetail">
     <Language ID="MatchInstalled" TargetProduct="O365ProPlusRetail" />
  </Product>
 </Add>  
</Configuration>

Learn more about how to use MatchInstalled in second-install scenarios.

If you're upgrading from a Windows Installer (MSI) version of Office, you can get Click-to-Run versions of the same language resources — for example, language packs, language interface packs, or proofing tools — installed when you install Microsoft 365 Apps. For more information, see Remove existing MSI versions of Office when upgrading to Microsoft 365 Apps.

To remove a language pack or proofing tool, you can use the Remove element, just as you would for a product. For product ID, specify LanguagePack or ProofingTools. In the example, the German language pack is removed across all installed products:

<Configuration>
  <Remove>
    <Product ID="LanguagePack">
      <Language ID="de-de" />
    </Product>
  </Remove>
</Configuration>

If you deploy Office from a local source on your network, you can use the Office CDN as a backup source for language packs that might not be available at that local source. To do so, use the same process and tools you used to deploy Office, such as Configuration Manager or the Office Deployment Tool.

When creating the configuration file in the Office Customization Tool, select Fallback to the CDN for missing languages in the installation settings of the Office Customization Tool.

When you install languages, the ODT looks first for source files in the source path location. If the language pack isn't available at that location and the Fallback setting is selected, then the ODT uses source files from the Office CDN.

When you use the ODT to download the installation files for Office to a folder that already contains that version of Office, the ODT conserves your network bandwidth by downloading only the missing files. For example, if you use the ODT to download Office in English and German to a folder that already contains Office in English, only the German language pack is downloaded.

Language-neutral product resources for Microsoft 365 Apps are packaged into a single file that contains all the neutral resources. Language-specific resources are packaged into language-specific files such as en-us for English (United States) resources.

The following table lists all the supported languages for Microsoft 365 Apps, along with culture codes and companion proofing languages.

Note

^[1] This language is only available for Version 2108 or later, but isn't available in Project or Visio.

• Overview of the Office Customization Tool
• Overview of the Office Deployment Tool
• Configuration options for the Office Deployment Tool
• Plan your enterprise deployment of Microsoft 365 Apps

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4