İlker GELİR

Thanks for sending me the file.

It's actually a very good example of how NOT to prepare XML for translators, but you can still handle it... albeit with a few small problems to overcome.

1. All the translatable text is in the attributes. This is very poor practice even though it does happen a lot.  Attributes should really be used to provide additional information/instructions about the element and should not contain the translatable text itself.  This is why Trados Studio could not extract the text out of the box because it has no clue that you actually want to translate it.
2. .Not the end of the world though, and least everything seems to be in just one attribute... the "text" attribute.  So you have to create a custom XML filetype and use one rule telling Trados to extract the text from the "text" attribute in every element (as they are different elements) in your file.  Like this:
   //*/@text
   This is a simple XPath expression that says extract all the text attributes (@text) in every element (//* - * is a wildcard).  You put it here:
   
3. Now if I open the test file (I made a shorter version with anonymised text):
   

So that gets you access to all the translatable text.  However, there is a problem because the text is also full of variables (& for example) and control characters (\r\n).  Not insurmountable but it  is a pain because you cannot use the embedded content processor for content coming from an attribute.  You can also see it comes from the attribute because of the TAG document structure here:

So you can either just work around this carefully as you translate, or you'll have to use something like the Data Protection Suite from the appstore to protect these characters as you work.

So in some ways a very simple problem as everything is in one attribute, but in other ways it's been made a little complex because of the additional content that as been placed in there.

I put the filetype I created here... might give you ahead start.

foxit_v1.zip

I also used an old XML filetype for this so it should be ok for whatever version of Trados Studio you have... unless you're using a really ancient one!

İlker GELİR

Thanks for sending me the file.

It's actually a very good example of how NOT to prepare XML for translators, but you can still handle it... albeit with a few small problems to overcome.

1. All the translatable text is in the attributes. This is very poor practice even though it does happen a lot.  Attributes should really be used to provide additional information/instructions about the element and should not contain the translatable text itself.  This is why Trados Studio could not extract the text out of the box because it has no clue that you actually want to translate it.
2. .Not the end of the world though, and least everything seems to be in just one attribute... the "text" attribute.  So you have to create a custom XML filetype and use one rule telling Trados to extract the text from the "text" attribute in every element (as they are different elements) in your file.  Like this:
   //*/@text
   This is a simple XPath expression that says extract all the text attributes (@text) in every element (//* - * is a wildcard).  You put it here:
   
3. Now if I open the test file (I made a shorter version with anonymised text):
   

So that gets you access to all the translatable text.  However, there is a problem because the text is also full of variables (& for example) and control characters (\r\n).  Not insurmountable but it  is a pain because you cannot use the embedded content processor for content coming from an attribute.  You can also see it comes from the attribute because of the TAG document structure here:

So you can either just work around this carefully as you translate, or you'll have to use something like the Data Protection Suite from the appstore to protect these characters as you work.

So in some ways a very simple problem as everything is in one attribute, but in other ways it's been made a little complex because of the additional content that as been placed in there.

I put the filetype I created here... might give you ahead start.

foxit_v1.zip

I also used an old XML filetype for this so it should be ok for whatever version of Trados Studio you have... unless you're using a really ancient one!