This macro's purpose is to allow you to flag text in your original language document (English in my case) so that when you export to XLIFF to hand off files for external translation, that the content is ignored by translation, and retained in the translated document in English. (For those cases where some text needs to remain only in English, such as legal, trademarks, brand names, etc.)
But when I use the Scroll Export to XLIFF and then review the exported .xlf files, the Scroll Non-Translatable macro and all its contained content is completely missing from the files. It apparently is removing the macro and its content instead of performing the intended function. Does anyone else see this? Is it a known issue/bug?
Does anyone have any other tips for marking up "non-translatable" content in Confluence Cloud/Scroll documents?
I did email K15t support, but they can be slow to respond. :(
Hi Steve,
I'm Johanna from K15t, the app vendor behind Scroll Documents. We're sorry you're running into issues with the Scroll Non-Translatable macros.
The content inside the Scroll Non-Translatable and Scroll Non-Translatable Inline macros should appear in the XLIFF export. They will just be marked in a specific way to prevent the content from being translated.
To troubleshoot this further, we'll need to have a look at the affected content. We have replied to your support ticket so we can continue troubleshooting there.
Cheers,
Johanna (K15t).
Hi @Steve Fazio ,
So in our Scroll document, the XLIFF export and the macro work as expected. Currently, however, only with the legacy editor in practice. This is what it looks like in XLF:
Do you use it inline or block?
I don't know how else you could mark it if you want to use this app and an XLIFF export.
Best,
Volker
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.