Alan Patrick Hynds Carr 

Alan Patrick Hynds Carr said:

As I do this quite often, I'd like to basically do it "on the fly". 

This is only possible in Studio if you have a supported format, and bitext files are not supported.  So you will have to convert first.

Having said that... you could use PowerShell to interact with the API for Studio and create a script that does that conversion automatically for you... that would be quite a neat solution and most likely fairly straightforward to do.

Thanks, Paul. 

That sort of automation is what I'm looking for. 

Would you mind pointing me to where I can more out find about a "Powershell" and "API for Studio"?

Best, 

Alan Patrick Hynds Carr 

Great... here's a few resources to get you started:

https://github.com/RWS/Sdl-studio-powershell-toolkit

https://multifarious.filkin.com/2024/08/31/trados-studio-powershell-trilogy-part-1/

Alan Patrick Hynds Carr 

I am very interested in this. Could you post your procedure once it's set up? Do I understand correctly that you attempt to do a pre-processing/file conversion, handing over to Trados, and then, I guess some kind of post-processing with PowerShell? And tie it all into Studio using the PowerShell Toolkit? That would indeed be very interesting.

Alan Patrick Hynds Carr Daniel Hug 

Wanted to have a little play with this so you might find this helpful too:

https://github.com/paulfilkin/Powershell_scripts/blob/main/mAT_Studio_Powershell/Scripts/06_upgradeBitexts.ps1

I based the script on a sample bitext format like this:

<?xml version="1.0" encoding="utf-8"?>
<bitext>
    <record wuid="a1234567b8c9d0e1f2g3h4i5j6k7l8m9">
        <eng><![CDATA[Welcome to our website!]]></eng>
        <fra><![CDATA[Bienvenue sur notre site web !]]></fra>
        <dom><![CDATA[WEB]]></dom>
        <his><![CDATA[UA 2025/04/01]]></his>
    </record>
    <record wuid="b2345678c9d0e1f2g3h4i5j6k7l8m9n0">
        <eng><![CDATA[Please contact our support team.]]></eng>
        <fra><![CDATA[Veuillez contacter notre équipe de support.]]></fra>
        <dom><![CDATA[SUP]]></dom>
        <his><![CDATA[UA 2025/04/01]]></his>
    </record>
</bitext>

So you'll probably need to amend it, but the script is all powershell and does this:

1. Prompts the user to select a Bitext XML file using a file picker dialog.
2. Converts the Bitext XML into a valid TMX file.
3. Automatically detects source and target languages from the TMX.
4. Prompts the user to confirm or update language codes.
5. Creates an SDLTM in the same directory as the input file.
6. Imports all TMX content into the new SDLTM.

I only tested this with my simple file, but as a POC it seems useful:

Alan Patrick Hynds Carr Daniel Hug 

Wanted to have a little play with this so you might find this helpful too:

https://github.com/paulfilkin/Powershell_scripts/blob/main/mAT_Studio_Powershell/Scripts/06_upgradeBitexts.ps1

I based the script on a sample bitext format like this:

<?xml version="1.0" encoding="utf-8"?>
<bitext>
    <record wuid="a1234567b8c9d0e1f2g3h4i5j6k7l8m9">
        <eng><![CDATA[Welcome to our website!]]></eng>
        <fra><![CDATA[Bienvenue sur notre site web !]]></fra>
        <dom><![CDATA[WEB]]></dom>
        <his><![CDATA[UA 2025/04/01]]></his>
    </record>
    <record wuid="b2345678c9d0e1f2g3h4i5j6k7l8m9n0">
        <eng><![CDATA[Please contact our support team.]]></eng>
        <fra><![CDATA[Veuillez contacter notre équipe de support.]]></fra>
        <dom><![CDATA[SUP]]></dom>
        <his><![CDATA[UA 2025/04/01]]></his>
    </record>
</bitext>

So you'll probably need to amend it, but the script is all powershell and does this:

1. Prompts the user to select a Bitext XML file using a file picker dialog.
2. Converts the Bitext XML into a valid TMX file.
3. Automatically detects source and target languages from the TMX.
4. Prompts the user to confirm or update language codes.
5. Creates an SDLTM in the same directory as the input file.
6. Imports all TMX content into the new SDLTM.

I only tested this with my simple file, but as a POC it seems useful:

Thanks for going to the trouble, Paul. 

As noted, I haven't had a chance to try this out. I guess it will take a little figuring out on my end, but it looks like it may well be worth the effort. 

Thanks again,