Guillaume Goemanne 

Did you ever find a way forward to progress this?
I work best having your files and if you are able to do so,I maybe able to explore all options

But for now this is what I am wondering: 

I know you mentioned Excel files but we do have a very good multi-lingal excel file type equally we have a multi-lingual XML file type, both of which can be downloaded from the Trados AppStore.
I mention alternative file types as these  both support embedded content processing and context / length checks and I assume from your post that your findings are using the default standard file types.

Secondly to explore out the box features that help with length restrictions and regardless of your parser rules, have you tried to implement this

, 

Regards

Lyds

Guillaume Goemanne 

Did you ever find a way forward to progress this?
I work best having your files and if you are able to do so,I maybe able to explore all options

But for now this is what I am wondering: 

I know you mentioned Excel files but we do have a very good multi-lingal excel file type equally we have a multi-lingual XML file type, both of which can be downloaded from the Trados AppStore.
I mention alternative file types as these  both support embedded content processing and context / length checks and I assume from your post that your findings are using the default standard file types.

Secondly to explore out the box features that help with length restrictions and regardless of your parser rules, have you tried to implement this

, 

Regards

Lyds

 Lydia Simplicio 

Hi Lydia, thank you for taking a look, I didn't think this thread would still be somewhere visible.

I never really got further than what I described back then:

- Custom XML file type

- Length restrictions preserved in the editor through parser rules

- HTML-tagging processed through embedded content processing based on DSI

I couldn't solve the entity problem until now. The file type's entity settings don't seem to touch them when they're inside of HTML tags:

As for your other suggestions:

- I love the multilingual Excel file type but it doesn't work in his case: the client's Excel file contains multiple columns per language, which is custom for Amazon projects.
(e.g. German title - English title - French title - German bullet point 1- English bullet point 1- French bullet point 1 etc.)

- I've also tried playing around with the multilingual XML file after I read some of Paul's articles on XPath, but I'm still struggling to make it work here. I think this XML structure doesn't fit the concept, as I need to exclude some untranslatable paths that are on the same level as the translatable ones.

- As for the length verification checker, it can only check one specific length restriction, but there are different ones depending on the module. That problem I was able to solve using the parser rules, but they disappear as soon as I activate one of the embedded content processor file types.

Unfortunately I can't send you the client's file itself, so I understand it's tough to really help me out with this. I was hoping I might come across someone with a similar problem and a solution that works for mine.

All best,

Guillaume