Giovanni Giusti

I work with multiline XML about every day and never had content skipped... but with XML of course there are so many parser settings... Without knowing your parser settings it's hard to say much...

Daniel

Thanks for your offer of help Daniel! 

The settings file is here - nothing too strange:

https://www.dropbox.com/s/aovabkousk3bq1t/parsersettings.sdlftsettings?dl=0

The same settings were used in Trados 2014 without any problems.

The TM also is set to recognize new lines as segment boundaries, according to these instructions:

http://noradiaz.blogspot.com/2014/01/adding-soft-return-segmentation-rule-to.html

If you look at this picture:

https://www.dropbox.com/s/l1vcl1zluhnxnqw/blockedtext.png?dl=0

The text in blue is blocked (and should be blocked); the text in green is translatable and should be translatable. But the text in red is missing from the Trados interface:

https://www.dropbox.com/s/a1steml7bhrci27/trados.png?dl=0

Unfortunately NDA limits the amount of content I can share, but I really can't see anything that would cause this. 

Thanks in advance for your insights!

Giovanni

Giovanni Giusti

Could you provide a relevant part of an XML file, a part where a segment is missed?

Daniel

Yes, it's the one I linked to before:

https://www.dropbox.com/s/l1vcl1zluhnxnqw/blockedtext.png?dl=0

Thanks again!

I was hoping for a proper xml file with root element and all, so that I can toy around with your parser settings...

Daniel

Hi Daniel, that would be great!

So, I extracted the single XML asset that is giving me problems into a new file, and tried again (same exact error occurs with the same segments). Then I changed all the translatable text to random words by pseudo-translating the file to en_GB to respect customer NDA. The only words that were not randomly changed are the ones that Trados did not see - and which are the ones in red in the previous picture.

I tested this file and it blocks out the right content in Trados (apart from the two items that should not be blocked):

https://www.dropbox.com/s/uyd2upbtk269k6m/test%20for%20daniel%20%282%29.xml?dl=0

Thanks again!

Giovanni

Giovanni Giusti

to my profound surprise, I could not get your settings file to work for me at all - Studio did not accept the placeholder settings for your legacy embedded content processor....

However, using a new embedded content processor it's a piece of cake - or at least it looks like it is. Would this be the content you would like to see in the Editor?

(I did not copy all your parser settings as for the snippet you gave me only the //value setting seems to matter.)

Daniel

Yes...! So if I recreated the content processor it would work? This processor was originally created under Studio 2011 and then reworked many times, I wonder if that corrupted it?

Giovanni Giusti

hard to say why it did not work ... for me, not even the <.*?> placeholder rule worked, so it was all a complete mess. Setting up the new filetype is about 5 minutes of work, you choose XML (embedded content), then the same parser settings as your old filetype, then in "Embedded content" this:

And then under "Embedded Content Processors"-Plain text-Inline tags you define what you want to exclude from translation:

Hope this is a help.

Daniel

Brilliant it worked! I was using "legacy embedded content"... maybe that's what did not work.

Thanks so much Daniel, I owe you a beer!

Giovanni

Hi Giovanni Giusti

I don't full yunderstand why your file type did not work, it should be possible to do this with the legacy embedded content file type, but I think it's obvious that it's easier with the new embedded content processor file type. Something might have become corrupted over time. Probably not worth digging into since you have a working solution now.

Beer: What about something else instead? Read my idea about improved document structure information an consider supporting it: https://community.sdl.com/ideas/translation-productivity-ideas/i/trados-studio-ideas/enable-more-document-structure-information-when-using-the-embedded-content-processor

Or verify my suggested answer.

I'll take either as a digital beer!

Have a great evening!

Daniel

Thank you! I owe you!

Thank you! I owe you!