The "type" and "x" attributes are optional, so this is only specific to TMX files generated by SDL.
Example:
<bpt i="1" type="16" x="4" />
What does the "type" and "x" attributes mean?
* Background:
I want to generate TMX files for used with Trados Studio, for now I am just going to ignore those attributes.
Hi Patrik
Thanks, that was helpful.
Can you tell me the corresponding numbers for the "type"?
The recommended values for the type attribute, when used in <bpt> and <it> are as follow (this list is not exhaustive):
- "bold" = Bold.
- "color" = Color change.
- "dulined" = Doubled-underlined.
- "font" = Font change.
- "italic" = Italic.
- "link" = Linked text.
- "scap" = Small caps.
- "struct" = XML/SGML structure.
- "ulined" = Underlined.
Unknown said:I don't think we actually use the type at all. The way the tags are resolved is not using that information so I would skip it.
Though you should know better, I tend to disagree ;-). At least regarding how Studio 2017 works, don't know if anything has changed in Studio 2019 in this regard.
During my investigation of https://community.sdl.com/product-groups/translationproductivity/f/90/t/13675 and https://community.sdl.com/product-groups/translationproductivity/f/90/t/13836 I found out that if "x" attribute is missing, Studio uses the information in "type" attribute for pairing the tags between source and target segment.
Jesse Good: I've seen Studio simply putting a (sequential) number in the "type" attribute. The following quote from my instruction for engineers on how to fix TMX affected by the above mentioned alignment issues might help you to understand how it works:
From the text in following source and target segments it's clear that the first "bpt" tag in target corresponds to first "bpt" tag in source and second "bpt" tag in target corresponds to second "bpt" tag in source. Therefore the fix will be to change the "59" attribute value to "57" and the "60" attribute value to "58".
<seg>For more information, see <bpt i="1" type="57"/>Select Marks<ept i="1"/> and <bpt i="2" type="58"/>Pan and Zoom<ept i="2"/>.</seg>
<seg>Weitere Informationen finden Sie unter <bpt i="1" type="59"/>Auswählen von Markierungen<ept i="1"/> und <bpt i="2" type="60"/>Schwenken und Zoomen<ept i="2"/>.</seg>
Unknown said:I don't think we actually use the type at all. The way the tags are resolved is not using that information so I would skip it.
Though you should know better, I tend to disagree ;-). At least regarding how Studio 2017 works, don't know if anything has changed in Studio 2019 in this regard.
During my investigation of https://community.sdl.com/product-groups/translationproductivity/f/90/t/13675 and https://community.sdl.com/product-groups/translationproductivity/f/90/t/13836 I found out that if "x" attribute is missing, Studio uses the information in "type" attribute for pairing the tags between source and target segment.
Jesse Good: I've seen Studio simply putting a (sequential) number in the "type" attribute. The following quote from my instruction for engineers on how to fix TMX affected by the above mentioned alignment issues might help you to understand how it works:
From the text in following source and target segments it's clear that the first "bpt" tag in target corresponds to first "bpt" tag in source and second "bpt" tag in target corresponds to second "bpt" tag in source. Therefore the fix will be to change the "59" attribute value to "57" and the "60" attribute value to "58".
<seg>For more information, see <bpt i="1" type="57"/>Select Marks<ept i="1"/> and <bpt i="2" type="58"/>Pan and Zoom<ept i="2"/>.</seg>
<seg>Weitere Informationen finden Sie unter <bpt i="1" type="59"/>Auswählen von Markierungen<ept i="1"/> und <bpt i="2" type="60"/>Schwenken und Zoomen<ept i="2"/>.</seg>
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
I don't think so ;-).
The first answer is about the "x" attribute, since this is exactly what it's for (ref. to the Patrik's link to TMX spec, it leads to "x" attribute specification). It's used as cross-reference between source and target tags, hence the "x"...
The second answer was not really about formatting... it's probably the list of recommended values what made you think it's about formatting, but the "type" attribute can (and does, as my examples show) contain anything.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
It's really not "what Patrik already said" ;-).
Patrik said that "type" attribute is (probably!) not used at all.
That's only partially true, according to my observations. The "type" attribute is not used only if "x" attribute si present. In that case the "x" attribute is used, since it's its purpose.
But if "x" attribute is NOT present, Studio still tries to pair the tags using the "type" attribute. And that's the information I added.
Translate
