I am in the process of translating our application (Pega 7.3.1) and have been through the localization export and import processes many times without issue. The localization wizard generates a file TextToTranslate.xml which is to be opened in Excel and then you re-import it to Pega in the same format. But now our organization has just upgraded to Office 2016 and they have blocked the opening of xml files in Excel. I can no longer edit/save/copy any of the file.
Has anyone encountered this issue before? Is there a workaround? Can Pega accept a different file format for importing translated text? I am stuck.
***Edited by Moderator Marissa to update platform capability tags****
Since the XML is just plain text, you could theoretically edit this manually in some other text editor. However, it will be quite cumbersome doing it that way. But it may unblock you.
I do not believe the localization wizard accepts other file formats, as it is expecting the file name and type which was generated by the product. So if you replaced it with something else, I believe it will act as though the file is missing.