Hello Sandra,

unfortunately not - and given that Paul's (copy + overwrite afterwards) and my (copy + delete beforehand) workarounds are each only two simple steps, I would be surprised if SDL put energy in developing this into a transparent process within Trados.

Also fortunately, most clients nowadays send me website content either as Word docx, or as an effortlessly imported XML/XLIFF file from the CMS's translation component. The barebone HTML approach remains a rare exception.

Happy New Year
Christopher

Hmmm, the only logical approach is of course to simply take the original source structure and copy the exported localized structure into it, overwriting the original source files... simply because everybody KNOWS that Studio exports only the localized files...
Why would anyone think about any other process?
And more importantly - why would TRANSLATOR care about this? This is a task for the client!

But I'm rather wondering who would send such garbage (I mean the complete structure including useless JavaScript, CSS and other files) for localization?!?!
Perhaps someone who was given a responsibility for a task (s)he has absolutely no idea about? I've seen too many such cases to think about any other option...

These days all web content is managed using a database-based CMSs creating the web pages dynamically, so localizing the rendered static HTMLs (most probably obtained using some website downloader like HTTrack, Offline Explorer or similar) is a total nonsense.