Forum Discussion
KellyMeeker1
7 years agoCommunity Member
NEW in Rise: Export for Translation
If you need to create courses in multiple languages, you’re going to love this new Rise feature. It allows you to export your course text to an XLIFF file* and then reimport it once it’s been transl...
pedro
5 years agoCommunity Member
We're having an issue with xliff files generated from Rise 360 which we translate. It is that every paragraph is enclosed by a g element, for example
<trans-unit id="items|1|answers|0|title"><source><g id="tSAGXrO37EMvKsgh" ctype="x-html-p">True</g></source></trans-unit>
This is annoying because they appear as tags in the translation editor. Is there anything our client can do to stop this from happening? There is some actual formatting also enclosed by g elements, so I don't think deselecting "Include HTML formatting" on export is an option. Is it not possible for Rise 360 to assume a paragraph on every source and target element without it having to be spelled out like this? I believe the source element permits non-xliff attributes, so could it not be done that way?
Thanks