Johannes Purer 

That is odd. The only factors I could think of would be: precise language code mappings between your File Type settings and your project.
Example French France vs French Canadian?

Also, do you have any filters within the file type defined, specifically as English level?

If some source rows are except from importing in, but these rows then correlate with where you have target translations, the entire row will confirm to source handeling.

Are you able to safely share your file?

Lyds

Johannes Purer 

Perhaps you didn't run the import multilingual translations (Excel) batch task to bring them in?

Hi Paul,

thanks a lot for this eye-opener! This worked, of course. :-)

Sorry for my ignorance, but I have never thought of having to import the text after the project has been created in Studio.

I have assumed, that this import is done automatically during the creation of the Studio project, as I am asked if I want to exclude the content or not. So the decision to include the content was made there, so why is it then not imported right away?

Does not matter, I know now that I first have to import the text.

Thanks for your help,

Johannes

PS: Lydia, thanks a lot also for your help!

Johannes Purer 

Always worth reading the instructions ;-)

https://community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/6290/multilingual-excel-filetype#mcetoc_1g2pv4tok4

Johannes Purer said:

so why is it then not imported right away?

The difference here is that we have used the APIs to create a filetype that is not supported out of the box.  We did this twice in fact, once for Excel and once for XML.  Using the APIs has some limitations as we don't have access to everything that a Trados Studio developer would have access to via the core product (a developer would understand this... tell me if you want more of an explanation).  So to work around this we had to use an import task after the project was completed to bring all the content in.

f you have the Professional version it's less of a problem since you can create a custom task to do all of this when you prepare your project.  But with the Freelance version you need to create your project and then run the import batch task afterwards.  Not a big deal, but it's something you wouldn't know if you didn't read the manual ;-)

you are right, blame on me. But maybe this is a hint for the developers of that data type to include the import right away. Thanks.

Johannes Purer 

Johannes Purer said:

But maybe this is a hint for the developers of that data type to include the import right away.

I'm 100% sure we know this already!  Read this again!

Paul said:

The difference here is that we have used the APIs to create a filetype that is not supported out of the box.  We did this twice in fact, once for Excel and once for XML.  Using the APIs has some limitations as we don't have access to everything that a Trados Studio developer would have access to via the core product (a developer would understand this... tell me if you want more of an explanation).  So to work around this we had to use an import task after the project was completed to bring all the content in.