Claudia Franco

As you identified I think the problem is that you have different source AND different target languages.  I did a quick test:

The source language changes are picked up correctly (und das könnte Ihnen helfen Alide Folz... vielleicht haben Sie die Sprache in dieser Ansicht einfach nicht hinzugefügt?) but I don't think the app is designed to expect a different target language as well.  I also think it would be tricky to handle because when you start adding this many unknowns how does the software know what language you want in there?

Perhaps an idea is this:

1. translate all the English to Spanish
   
   
2. then filter on the untranslated:
   
   
   
3. Use studioViews from the appstore to export this filtered view as an SDLXLIFF.
   
   
   
4. Change the language codes in the exported SDLXLIFF so they are the other way around like this (Studio needs this to be able to open the file with the languages you need):
   
   
   
5. Translate this file with your es-en TM:
   
   
   
6. Save the file, and then import it back with studioViews.  No need to reverse the language codes back to what they were... studioViews actually ignores the codes as it uses another mechanism for this:
   
   
   
7. And hey presto... I'm done:
   

Not perfect by any means, but perhaps it'll help?

Claudia Franco

As you identified I think the problem is that you have different source AND different target languages.  I did a quick test:

The source language changes are picked up correctly (und das könnte Ihnen helfen Alide Folz... vielleicht haben Sie die Sprache in dieser Ansicht einfach nicht hinzugefügt?) but I don't think the app is designed to expect a different target language as well.  I also think it would be tricky to handle because when you start adding this many unknowns how does the software know what language you want in there?

Perhaps an idea is this:

1. translate all the English to Spanish
   
   
2. then filter on the untranslated:
   
   
   
3. Use studioViews from the appstore to export this filtered view as an SDLXLIFF.
   
   
   
4. Change the language codes in the exported SDLXLIFF so they are the other way around like this (Studio needs this to be able to open the file with the languages you need):
   
   
   
5. Translate this file with your es-en TM:
   
   
   
6. Save the file, and then import it back with studioViews.  No need to reverse the language codes back to what they were... studioViews actually ignores the codes as it uses another mechanism for this:
   
   
   
7. And hey presto... I'm done:
   

Not perfect by any means, but perhaps it'll help?

Hi Paul,

I've just tried your solution and it works great! I'll just add a couple of tips here for anyone who also needs this workaround:

In step 4, in order to change the source and target languages, open your sdlxliff file using Notepad (Bloc de notas in Spanish), not Wordpad. I opened it in the latter first, and my sdlxliff file ended up corrupted. Then I did the same in Notepad, and it worked great.

In step 5, you do not need to use a different TM. When you open your newly created sdlxliff file with reversed source and target languages (SP>EN), you just open your regular EN>SP TM using AnyTM, and Studio will automatically reverse the TM's languages.

Paul, please do correct me if any of the above tips are wrong. Thanks a lot for having taken the time to look into this!

Claudia

Dear Paul! I came across this thread, because I need to filter and exclude segments with the language I do not want to translate (just copy the source into target and translate the rest).

For example, I have a document mostly in German and some parts in English. I need to translate these parts into German and deliver the document in German. 

How can I filter them? The advanced filter must allow that , I am sure, but I am unable to see that .... I have checked language detection, works perfect.

So how can I filter out the German texts I do not need to touch?

Thank you so much in advance!

Yulia Kovalskaya 

What kind of document?  A new thread might be better for this one!