When using the Optimize-M365Doc -UseTranslationFiles the OData api names will be translated to the labels used in the Microsoft Portals. Some of the documented objects are not translated due to high effort which is needed to do this. But you can help translating them and make the project better for everybody. With the new Invoke-M365DocTranslationUI command this is really simple.
| Image | Description |
|---|---|
 |
Most often you have already created a documentation and got the message that not all translations were available. Then you can start with step 3, otherwise you can now create a documentation from your environment. |
 |
Optimize the just collected infomration with the Optimize-M365Doc -UseTranslationFiles command. |
 |
The command will show you all OData api names which are not full translated. |
 |
You can now start the new translation UI by executing Invoke-M365DocTranslationUI. |
 |
Select the OData api name which you want to improve. |
 |
In this step you can translate all properties. You should follow these guidelines: |
-
Use the exact same name as it is in the Microsoft Portal
-
US English names
-
Section name
- Use "Basic" or Empty when no section can be dedected in the Microsoft Portal
- Use "/" to separate Sub sections
| |
| Click on Save for local testing. This saves the translation file into the local module directory. |
| 
| You can now execute the Optimize-M365Doc -UseTranslationFiles command again and create a new Word documentation file. |
| 
| Open the newly created Wiord file and check if the translation is as wished. If yes continue to the next step. Otherwise go back to step 6. |
| 
| Start the Invoke-M365DocTranslationUI again and select the translated OData api name and then submit the translation in the 4 - Submit register. |