Forum Discussion
NEW in Rise: Export for Translation
Hello, Pedro!
What translation tool are you using?
The <g> tags are required for many translation tools, including SDL Trados and Smartcat. The tags enable the translation tool to translate formatted text (such as bold, italic, color and font size). Without the <g> tags, the file is not translatable in those tools.
If you have more questions about that, we're here to help!
I understand that <g> tags are required to preserve formatting, which is fine. What's causing a problem is, as I say, when they are used to indicate an html <p> tag. Here is another example:
<trans-unit id="items|80|items|0|heading"><source><g id="8asNiPqNRyLjc3us" ctype="x-html-p"><g id="4T8XVNh-vPCU4aXZ" ctype="x-html-strong">New approaches</g></g></source></trans-unit>
The second nested g element indicating <strong> tags is not a problem. But the first one indicating a <p> tag is. Nearly every <source> element in the files we receive begins like this, apart from the varying id:
<source><g id="8asNiPqNRyLjc3us" ctype="x-html-p">
Is there another way for the author to indicate a paragraph without these extra g tags being generated? Or for the system to know to insert p tags without needing these extra g tags within the <source> element?
- Crystal-Horn5 years agoStaff
Thanks for clarifying, Pedro. There isn't a way to export your translation without those tags at this point, but I'll tag this discussion to update you with any changes we make that will help.
- pedro5 years agoCommunity Member
Would it not be possible to have every paragraph as a separate source element, like this?
<source id="8asNiPqNRyLjc3us" ctype="x-html-p">
You probably wouldn't even need the
ctype="x-html-p"
if the system knows that a <source> always corresponds to a <p>. The <g> tags delineating them would also not be necessary, and would only be present for inline formatting, which I believe is their intended purpose.