No arguments from me... the solution to provide all options has been tabled already.  Just need to wait for it to be implemented.

I'm interested in what you said about the length restriction being in the XML file though.  Does this mean you have variable lengths per segment?  If you do then why don't you just add a check into the parser rules so you get a QA warning when you exceed to allowable length for each segment?  This article explains:

https://multifarious.filkin.com/2014/05/02/xml-length-restrictions/

Regards

Paul

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

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:

Length Verification.zip

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

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:

Length Verification.zip

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