All sorted.

1. Normal Excel files were being picked up by the Bilingual Excel filetype because it was top of the list.  Resolution : uncheck it for 'normal' projects, or move it further down the list so it's not selected first for all Excel files.  Default position is below the 'normal' Excel filtype.
2. Bilingual files only extracted on segment because column A of the file only had one segment in it.  The rest of the contents were elsewhere in the file.

Regards

All sorted.

1. Normal Excel files were being picked up by the Bilingual Excel filetype because it was top of the list.  Resolution : uncheck it for 'normal' projects, or move it further down the list so it's not selected first for all Excel files.  Default position is below the 'normal' Excel filtype.
2. Bilingual files only extracted on segment because column A of the file only had one segment in it.  The rest of the contents were elsewhere in the file.

Regards

Hi,

The problem is that all excel files have the same extension, either xls or xlsx.  So Studio doesn't know if you want your excel to be handled as a bilingual excel file or not.  Studio just takes the first Excel file that fits the extension in the list of filetypes.  So here if you add an xlsx file for tranlsation it will always take this one:

With this Bilingual Excel filetype Studio looks for various settings relating to where the translatable content should be (in which column) and where the translation should be placed (a different column).  So if you don't want this bilingual Excel filetype to be used because you have a monolingual Excel file where the entire file just needs to be translated so the target file is just a fully translated version of the source then you need to address the options appropriately.

You either deselect the bilingual file like this:

Or move it below the monolingual Excel like this:

If you do this in the default Project template, which is effectively File -> Options -> File Types then the change will affect all new Projects using the defaults, and all projects created using the Translate Single Document workflow.

But sometimes it's easier to just create a new project template that puts the Bilingual first so it's different to the default and then when you need it you just create a project by selecting the project template that has this bilingual excel first.

You can find a bit more on this particular bilingual excel filter here that might be helpful for you:

You didn't really explain what your problem was exactly so I hope this explains enough to help you resolve your issue?

Regards

Paul

Hi Paul,

Thank you for your quick answer. However, my problem has not been solved yet.

I will go into the details as below so that u could understand:

+ My excel file contained a lot of contents. However, when it was opened by sdl trados, it showed few contents which turned out to be numbers. See picture below.

+ When I deselected bilingual excel file type according to your suggest, it failed to open:

So, plz give me an advice to address this problem.

Thanks a lot.