Word macros for Translation file

[Cheryl_May]

Hi Community,

Our author encountering this notice in producer while importing translation.docx file. This is a recurring issue since last year. 

While doing internal investigation, I came across the following:-

1. File path: When we export the translation file it was downloaded by default in docx format to our machine. But the document type change to dotm during uploading. Not sure if this is something to have a closer look that causes the error.

2. It appears the Macros in the document was not allowed in our organization. We have global policy which cannot be changed. 

While I hope to find a solution (perhaps it is available), for one of the option below. Preferably, option 1.

Option 1. Is there a translation file template without the need of macros and working as expected? Due to the translation accuracy, our authors and users has chosen this manual option compared to machine translation.

In addition, I have looked up Enable or disable macros in Microsoft 365 files,

Option 2. To have these 'macros' digitally signed in the Trust Center.

In order to do so, we have to obtain the new Trusted Publishers certificate SAP SE and periodically upload the certificate manually by each author in their machine. we have limited administration rights in our machine this may not be a long-term solution.

Much appreciate your help here.

[ShaneLipke]

Hi Cheryl,

Anton is correct, you should use the Machine Language Translation option if you are translating to supported languages.  If you translating content into languages that are not supported by SAP Translation Hub, the service performing the Machine Language translations for Enable Now then you will have to continue to use the current option.  

I just tested the manual translation capability and you are correct that a .docx document is generated during the export.  .docx documents do not contain macros.  I then imported the modified content and the file extension remained as .docx, it was not converted to .docm.  .docm files can contain macros but these macros are not coming from Enable Now. 

Please ensure that when you update and save the .docx document generated from Enable Now that it is being saved as a .docx file.  If it is, Producer will not update the file type and insert macros during the import.

Regards
Shane