Hi,
I received XLF files from the client - for the first time, not experience of working with them.
I managed to import them into Studio project, but found, that SDLXLIFF, except for the text for translation, contains a lot of service strings.
What can I do to obtain an SDLXLIFF only with the text for translation to comfortably translate and to correctly assess the translation volume?
Sergey
For tag pairs you should use
From what I see, the default tag regex (</?[\p{Ll}\p{Lu}]\w*[^<>]*>) converts pair tags already. But it doesn't convert this tag for example: <?xml version="1.0" encoding="UTF-8"?>
It does not convert tag pairs, it converts all recognized tags to placeables. As for the <?xml...>-tag: I would need to have the file to check it. But it looks like you just need a parser for xml with html embedded content.
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Well... My version does. This is what I get with the default tag regex alone:
Or maybe we have different understanding of paired tags and placeables (or placeholders?).
Or maybe we have different understanding of paired tags and placeables (or placeholders?).
You do.
You have just converted all the opening and closing tags to placeholders. If you want these to be handled correctly as a tag pair and not a placeholder you need rules for tag pairs.
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
You have a tag in front and in the end of the segment. So you need to enter them one by one. When you define a proper rule for <p> </p> tags, the wouldn't even appear in the segment. So far less effort for you and a significantly lower probability of errors.
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Ok, I tried your regex. They still appear. The only difference I see is that the tag placeholders now have opening/closing angles:
But I have to add all paired tags individually... Just for angles? How can I make them not even appear in the segment?
Ok, indeed - these are pairs already. But not declared as "may exclude" or even better "exclude".
And yes, all tags should be declared individually, as they have different meanings. <p> is paragraph and should be external, while <strong> is same as bold and should be included unless it covers the whole segment, when it can be excluded. But it mus be declared as internal tag.
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
But I have to add all paired tags individually... Just for angles?
Yes and no. You could create generic rules for all tag pairs, but if you want to apply appropriate formatting to represent what the tags mean you would obviously need to create separate tags for each pair. I also find that sometimes separate tags are better because some files where you use embedded content like this contain content that is not well formed at all and then you can get errors with a generic rule. Placeholders don't have that problem because the application doesn't look for form... just any old tag!
The only difference I see is that the tag placeholders now have opening/closing angles
They are also placeable using the appropriate shortcuts and checks to make sure you have the right tag in the right place. With placeholders it's much harder to control and much easier to make a mistake affecting the final file.
The reason you see them may be down to how you set up the advanced rules for inclusion... not sure.
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
But I have to add all paired tags individually... Just for angles?
Yes and no. You could create generic rules for all tag pairs, but if you want to apply appropriate formatting to represent what the tags mean you would obviously need to create separate tags for each pair. I also find that sometimes separate tags are better because some files where you use embedded content like this contain content that is not well formed at all and then you can get errors with a generic rule. Placeholders don't have that problem because the application doesn't look for form... just any old tag!
The only difference I see is that the tag placeholders now have opening/closing angles
They are also placeable using the appropriate shortcuts and checks to make sure you have the right tag in the right place. With placeholders it's much harder to control and much easier to make a mistake affecting the final file.
The reason you see them may be down to how you set up the advanced rules for inclusion... not sure.
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 also find that sometimes separate tags are better because some files where you use embedded content like this contain content that is not well formed at all and then you can get errors with a generic rule.
to make sure you have the right tag in the right place. With placeholders it's much harder to control and much easier to make a mistake
Ah... That makes sense now. Ok, I agree. Thank you both for your patient and detailed explanations.
Translate
