"Probability score": 0.7

"Question improvement suggestion": Please provide more details about the error message you received when trying to open the MHTML file in Trados Studio. Also, it would be helpful if you could share the exact version of Trados Studio you are using and your operating system.

In the meantime, based on the information you have provided, here is a suggested answer to your question:

Hello Sameh Ragab,

MHTML files are a web page archive format used to combine resources that are typically represented by external links (such as HTML files, images, and flash animations) together with HTML code into a single file. Trados Studio does not natively support MHTML files, which is why you're seeing a lot of strange HTML code appearing as segments.

Here's a workaround you can try:

Step 1: Open the MHTML file in a web browser.

Step 2: Save the page as an HTML file. Most browsers offer this option in the "File" menu.

Step 3: Open the saved HTML file in Trados Studio.

This should allow you to translate the content without the HTML code appearing as segments.

However, please note that this method might not work perfectly for all MHTML files, especially those with complex structures or embedded scripts.

As for your suggestion to introduce MHTML file type support in Trados Studio, I recommend submitting this as a feature request through the official channels. Trados Studio's development team regularly reviews these requests and may consider adding this feature in future updates.

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

RWS Community AI

it only offers to be saved as an mhtml and if I use the extension, the formatting gets completely distorted! 

 Sameh Elsharkawy 

This is the first time I have seen anyone asking for this (and mhtml has been around for nearly three decades), so I doubt there is a good usecase for creating a filetype for it.  The problem is MHTML is really a web page archive format.  It is useful for saving complete web pages for offline use or sharing, a bit like the reason for sharing a PDF, but isn't the best for translating.

Like PDF work it's always better to get the original html that the mhtml was based on.  You can convert a mhtml into html through your browser (not by renaming the extension, but by saving as html), but back conversion to mhtml might not preserve every interactive or dynamic feature perfectly.  Despite being around for so long, it's never been universally standardised across browsers, so some tools and platforms handle it differently or not at all.  I think it's mostly used today for archiving, and eDiscovery... for example.

So try using Ctrl+S in chrome after opening the mhtml and choose the html option to save it.  That should be better for you.

Dear Paul,

Your swift response is, as ever, a delight—truly, your inbox must quiver at the sight of my name! I suspect you secretly view me as a charming eccentric, wielding an arsenal of plugins and peculiar requests with the fervor of a seasoned Power user. Alas, after 33 years in this game, my work habits are less a lifestyle and more a lifelong love affair—change is but a distant dream.

In a twist of fate, I must confess the mhtml conundrum wasn’t my invention. A client, in their infinite wisdom, bestowed upon me a zip file brimming with these vexing files for translation. When Studio recoiled in horror, I turned to you, my knight in digital armor! To sidestep further chaos, I’ll kindly nudge my client toward HTML files—conversion games are a risky gambit, especially when word counts and target file fidelity hang in the balance.

Thank you for your ever-gracious support, Paul. Wishing you splendid days and hoping you’re thriving in grand style.

Warm regards,
Sameh

It is amazing how the AI is a game changer, even for improving replies to sound like they are coming from a native British speaker! I bet you laughed while reading my reply!!

Sameh Elsharkawy 

Indeed... English with a neo-Victorian tech aesthetic ;-)