Hi,
since the last update (SDL Trados Studio 2017 SR1), the shown number of characters in the active segment in the status bar in Editor on the right side above is now without the spaces! I do not find how to change this setting. Can you help me?
Please note: I'm translating strings with strict lenghts, I absolutely need to see the number of characters WITH space characters in the active segment to formulate the best translation.
Thank you in advance for your help!
Isabelle
Hi Paul
This is because the length is not given explicitely, but coded. For example, if a segment is preceded by a certain element, which coontent is 003 for example, you may use 30 characters. If this element is 0001, you have no limits and so on.
So from my knowledge it is not really easy to implement in any way.
This is how the file looks like:
So there is no corelation (at least not directly) between the limit and the translatable text.
Best regards, Jerzy
_________________________________________________________
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.
Thank you also from me, Paul
here what I see in my xml:
ending with 1 = 30 chars
ending with 2 = 10 chars
ending with 3 = 180 chars
Can you propose another solution?
so long
Isabelle
Thank you also from me, Paul
here what I see in my xml:
ending with 1 = 30 chars
ending with 2 = 10 chars
ending with 3 = 180 chars
Can you propose another solution?
so long
Isabelle
Hi Isabelle Hofmann and Jerzy Czopik
I have attached a zip file here with an example xml based on the screenshot you provided and also a settings file for Studio:
Basically I created three parser rules like this:
//*[contains(@FileKey, '00001')]/TextTranslate
//*[contains(@FileKey, '00002')]/TextTranslate
//*[contains(@FileKey, '00003')]/TextTranslate
Then I added some structure information to each one... for example this is for the one ending with 1:
Then I added a maximum length check in the advanced settings of the parser rule for each one:
Finally you check the option in the verification settings to use file specific limits for the length check:
And that's it. The result is that when you translate the file and go over the limit for each one you get a warning like this:
This is pretty useful because it not only picks up that you exceeded the limit but it also tells you what the count was so you know how many to reduce it by. In addition you get this handy reminder in the DSI column on the right showing what the restriction is when you hover over it:
And if you click on one you get this sort of information:
I love this stuff... it's where Studio really shines above any other translation tool. The capabilities available for handling XML are brilliant :-) Hopefully you'll find this is a useful method for you with these types of files. If you need more information check this post as I suggested earlier, it's Solution #3:
https://multifarious.filkin.com/2014/05/02/xml-length-restrictions/
Regards
Paul
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
Translate
