Office 2013 Proofing Tools
.If you're an administrator who has deployed a volume licensed version of Office 2016 to your users, you can from the Volume Licensing Service Center (VLSC).If you're an administrator who has deployed a volume licensed version of Office 2019 to your users, you can.Step 1: Install the language accessory packSelect the version of Office you're using from the tabs below, then select the language desired from the drop-down list. Then choose the appropriate architecture (32-bit or 64-bit) from the download links provided. If you're not sure what you're using seeOnce the file is downloaded, double-click it to install it.
Office 2013 Proofing Tools
This guide still works for Office 2016. (Both for OVS and 365)The following registry setting should be applied to allow Office to “Detect Language automatically”.REG ADD “HKCUSoftwareMicrosoftOffice16.0CommonLanguageResourcesEnabledEditingLanguages” /V LanguageCode /T REGDWORD /D “3” /FWhere LanguageCode is the language identifier of your installed proofing tools. Example: nb-noWhen installing the application as system, make sure you run the REG ADD in user-context or set the value in GPO, for it to be applied correctly. PowerShell App Deployment Toolkit has the excellent “Execute-ProcessAsUser” and “Invoke-HKCURegistrySettingsForAllUsers” that also can be used.