Mike Rodent 

Just a suggestion...

Mike Rodent said:

By converting all tables to text in both files, then converting all text to tables, then making these two vertical columns in the same Word file, I then made an Excel file.

Once you have the Excel file why don't you just open that in Trados Studio as a bilingual Excel?  That would be by far the easiest solution to what you're trying to do.

Mike Rodent 

Just a suggestion...

Mike Rodent said:

By converting all tables to text in both files, then converting all text to tables, then making these two vertical columns in the same Word file, I then made an Excel file.

Once you have the Excel file why don't you just open that in Trados Studio as a bilingual Excel?  That would be by far the easiest solution to what you're trying to do.

Thanks. ******* I DON'T KNOW WHETHER MY POSTS IN THIS THREAD ARE GETTING THROUGH TO YOU MODS ********

Earlier today I said this:

Thanks.

I ran the plugin for v 2019 (apparently successfully), then closed and re-opened SDL, before doing this. 

There is no "Add" button. There is a "New" button ... but I couldn't add TMX. But there was a new link on the "File types" page. This let me do it. Link then disappeared.

Then I tried creating a new project... added the TMX file, .... and got a dreaded Error message: "The source language of this file (French) is different from the project source language".The thing wouldn't open (i.e. wouldn't process the .tmx file).

This is incorrect. Under language pairs there is "All Language Pairs" and under that "French (France) --> English (United Kingdom)". Furthermore, when I open that .tmx in Olifant (with all the TUs, perfectly aligned) it says very clearly Source: FR, Target: EN.

Any suggestions?

 ***Mods***: this setup whereby every answer has to be modded is excruciatingly tiresome. So yep, addmittedly characteristic of the app itself. But maybe you should, er, make things less annoying. I can't edit my posts after submitting, and have no idea what you have got or seen, or when you are going to "approve" posts.

Now trying to find out about the "bilingual Excel file" solution. I currently have no idea how that works... 

Hello ... are ANY of my posts getting through? This is extremely annoying. I can't see ANY of my posts in reply. Please SORT THIS OUT.

Mike Rodent 

I have just taken you off moderation.  Your first post into this community was yesterday and we always put all new users on moderation until we know they are really users we want posting.  If you saw how much spam we get, that I guarantee our users would not want to see in here (and it's getting harder to spot with AI improving the nonsense we used to see), then you would understand.

So might be annoying, but it's for your benefit.

 Mike Rodent 

Mike Rodent said:

Now trying to find out about the "bilingual Excel file" solution. I currently have no idea how that works... 

This might be useful - https://multifarious.filkin.com/2015/09/28/bilingual-excel-and-stuff/

OK thanks. I thought it might be something like that. But by God it's annoying.

Earlier today I said this (replying to Jesús):

Thanks.

I ran the plugin for v 2019 (apparently successfully), then closed and re-opened SDL, before doing this. 

There is no "Add" button. There is a "New" button ... but I couldn't add TMX. But there was a new link on the "File types" page. This let me do it. Link then disappeared.

Then I tried creating a new project... added the TMX file, .... and got a dreaded Error message: "The source language of this file (French) is different from the project source language".The thing wouldn't open (i.e. wouldn't process the .tmx file).

This is incorrect. Under language pairs there is "All Language Pairs" and under that "French (France) --> English (United Kingdom)". Furthermore, when I open that .tmx in Olifant (with all the TUs, perfectly aligned) it says very clearly Source: FR, Target: EN.

Any suggestions?

In addition to finding out what's wrong there, I'm now trying to find out about the "bilingual Excel file" solution. I currently have no idea how that works... Found a vid though.

NB a "bilingual Excel" solution is not ideal, because I would then need to reconstruct the re-read Word file. 

Thanks, will give that a read a bit later.

Mike Rodent 

Mike Rodent said:

This is incorrect. Under language pairs there is "All Language Pairs" and under that "French (France) --> English (United Kingdom)". Furthermore, when I open that .tmx in Olifant (with all the TUs, perfectly aligned) it says very clearly Source: FR, Target: EN.

Does it say fr-FR and en-GB?  Or just very clearly the wrong thing?

You mean in Olifant? It says "Source: FR" and "Target: EN". That's all it says.

Could there be some way of editing some bytes of the .tmx to make it says PRECISELY what SDL needs it to say, if "fr-FR" / "en-GB", for example? I have Notedpad++ and have some experienced of this byte-level intervention due to some of the most infuratingly intractable SDL errors.

 Mike Rodent 

Mike Rodent said:

You mean in Olifant? It says "Source: FR" and "Target: EN". That's all it says.

Yes... and probably in a text editor too.  You don't need Olifant just to look at a TMX.  Does the file look like this:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE tmx SYSTEM "tmx14.dtd">
<tmx version="1.4">
  <header
    creationtool="ExampleTool"
    creationtoolversion="1.0"
    segtype="sentence"
    adminlang="EN"
    srclang="FR"
    datatype="PlainText"
    o-tmf="TMX"/>
  <body>
    <tu>
      <tuv xml:lang="FR"><seg>Bonjour</seg></tuv>
      <tuv xml:lang="EN"><seg>Hello</seg></tuv>
    </tu>
  </body>
</tmx>

Or this:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE tmx SYSTEM "tmx14.dtd">
<tmx version="1.4">
  <header
    creationtool="ExampleTool"
    creationtoolversion="1.0"
    segtype="sentence"
    adminlang="en-GB"
    srclang="fr-FR"
    datatype="PlainText"
    o-tmf="TMX"/>
  <body>
    <tu>
      <tuv xml:lang="fr-FR"><seg>Bonjour</seg></tuv>
      <tuv xml:lang="en-GB"><seg>Hello</seg></tuv>
    </tu>
  </body>
</tmx>

If it's not the latter then that might be your problem.  Just edit with a text editor - search and replace the language codes.

Excel is probably easier for you.

That did it ... thanks a lot!

("Verify answer" appears to mean "Thanks Paul, this is the accepted answer"). Unusual forum this one.