An additional language version makes your declaration accessible to more readers. It must convey the same technical content and follow the required review and publication process.
1. Confirm the source version and purpose
Select the EPD requiring another language. Establish whether you need a translation or additional target-market requirements. Creating a language version does not replace any additional calculations needed.
2. Add the language version
Choose the action to add a language and select an available target language. Check the inherited properties and documents. Available editing actions depend on permissions and document status.
3. Review the translation technically
Check technical terms, product names, units and tables. Any automatic translation offered requires review just as an external translation does. Keep language versions consistent when technical content changes.
4. Coordinate review and publication
Agree the required process with IBU and progress the language version through that workflow. A newly created language entry is not yet a published EPD. Check the version actually made available at completion.