Hello,

I understand your concern about the inconsistent behavior of the embedded content function in Trados Studio when dealing with reg-ex tags, especially when they are at the beginning of a sentence. This can indeed be challenging when working on game translations where such tags are common.

Here's a step-by-step guide on how you can try to resolve this issue:

Step 1: Open your project in Trados Studio.

Step 2: Navigate to the "Project Settings" and select "File Types".

Step 3: Find and select the file type that you are working with (for example, HTML, XML, etc.).

Step 4: In the settings for that file type, look for the "Embedded Content" section.

Step 5: Make sure that the regular expression (reg-ex) you are using to identify your tags is correctly entered and that the "Include in the beginning of the sentence" option is checked.

Step 6: Save your settings and try to open your file again.

If the issue persists, it might be due to a specific combination of tags and text in your file. In such cases, you might need to adjust your regular expressions to correctly identify and handle these instances.

Remember, regular expressions can be complex and powerful tools, but they also require careful handling to ensure they work as expected. It might take some trial and error to find the right expression for your specific needs.

I hope this helps! If you have any other questions or need further assistance, feel free to ask.

Best regards,

RWS Community AI

Yes, I understand that it can be complex. Yet as I've stated in the post, 

the following sentences
"<size=35><sprite=0></size><voffset=0.15em> {0} 훈련하기</voffset>"
"<size=30><sprite=2></size><voffset=0.15em> +{0} 고잉 홈</voffset>"

have the same pattern but the tags will only show up for one of them.

<sprite=2>{0} 경험치 UP
{0} 남음

and many others won't show up. 

Hello,

I understand your concern and it seems like a complex issue. The inconsistency you're experiencing might be due to the specific structure of the tags in your sentences.

Here's a suggestion on how you can try to resolve this issue:

Step 1: Open your project in Trados Studio.

Step 2: Navigate to the "Project Settings" and select "File Types".

Step 3: Find and select the file type that you are working with (for example, HTML, XML, etc.).

Step 4: In the settings for that file type, look for the "Embedded Content" section.

Step 5: Try to modify your regular expression (reg-ex) to make it more inclusive. For example, if your current reg-ex is specifically looking for tags at the beginning of the sentence, try to modify it to look for tags anywhere in the sentence.

Step 6: Save your settings and try to open your file again.

If the issue persists, it might be due to a specific combination of tags and text in your file. In such cases, you might need to adjust your regular expressions to correctly identify and handle these instances.

Remember, regular expressions can be complex and powerful tools, but they also require careful handling to ensure they work as expected. It might take some trial and error to find the right expression for your specific needs.

I hope this helps! If you have any other questions or need further assistance, feel free to ask.

Best regards,

RWS Community AI

tell me how I can make the sentences I've mentioned as inclusive reg-ex

Hello,

I understand that you're looking for a way to make your regular expressions more inclusive. Here's a step-by-step guide on how you can modify your regular expressions:

Step 1: Open your project in Trados Studio.

Step 2: Navigate to the "Project Settings" and select "File Types".

Step 3: Find and select the file type that you are working with (for example, HTML, XML, etc.).

Step 4: In the settings for that file type, look for the "Embedded Content" section.

Step 5: In the regular expression (reg-ex) field, you might want to use a more inclusive pattern. For example, if your current reg-ex is "^<size=\\d+><sprite=\\d+></size><voffset=\\d+.\\d+em> \\{0\\}", you could try changing it to "<.*?>\\{0\\}". This new pattern should match any tag followed by "{0}" anywhere in the sentence, not just at the beginning.

Step 6: Save your settings and try to open your file again.

Please note that regular expressions can be complex and powerful tools, but they also require careful handling to ensure they work as expected. It might take some trial and error to find the right expression for your specific needs.

I hope this helps! If you have any other questions or need further assistance, feel free to ask.

Best regards,

RWS Community AI

Keni Lee 

Keni Lee said:

It sucks that we can't full rely on trados not to have bugs like these.

Perhaps it's not a bug at all?  Please share a sample file that exhibits this behaviour for you.

Hey for anyone in the future who come here I think I figured out why this happens.

So I've noticed that trados can be very sensitive about the documents it gets fed.

I've taken the same document (which I found out that it was once a google spread in the past) and copy pasted into a new Microsoft Excel but when pasting I only pasted the value.

Which you can do by pressing ctrl then v after pasting the content.

This will for some reason get rid of this problem and will show all tags that might have been hidden even though you've set the regular expression correctly.

This also helps with trados sometimes getting errors when exporting.

Keni Lee 

Keni Lee said:

This will for some reason get rid of this problem

The reason is most likely that the regex is incorrect for the content you had there first.  It would be helpful if yo shared a sample file that actual has this problem so we could look at it and find out the real reason.  At the end of the day it's only a computer and it should do exactly what you tell it.  Even when it's a bug that would be true because it's doing what the developer told it, but when picking up text with regex it's important to see what is actually there in the underlying file.

Sure. Please share me an email since it's a client's document and I do not want to share it directed on the forum!

and for context the above is all I did I did not touch or adjust any of the Project setting's Embedded Content's Regular expression from when it had the problem and when the problem went away.

ps. this wasn't the only file that did this. every file I've dealt with that has been downloaded from google spread did this behavior.

Keni Lee 

Surely you can do this since I don't really want large documents to test:

1. copy the file
2. delete everything in it apart from the affected part
3. edit any text so it's meaningless in terms of being traceable back to your client

Keni Lee said:

ps. this wasn't the only file that did this. every file I've dealt with that has been downloaded from google spread did this behavior.

In that case it should be easy for you to create a small sample file to share?  I have no idea how to reproduce this issue so anything you can do to make this easy so we can try to help would be appreciated.