🚀 go-pugleaf

Slava,

Localization means translation. A localization vendor does translations into other languages. So, I think we are talking about the same thing, unless you have something else in mind.

But I think you misunderstand one thing. You nor the client need to implement any kind of CMS or translation memory. Typically, the client sends all the Frame files and any referenced image files to the translation vendor, who then translates the Frame files into whatever languages the client wants. The vendor uses software that uses translation memory; the client does not need to provide that software or do anything to the files. The translation memory for the files that are translated is saved to disk, which the vendor typically keeps, but which the client can request a copy.

When changes are made, the client sends the updated files to the translation vendor. Then vendor loads the translation memory saved from the first translation into his software, and then does the translation of the updated files. Where there are no changes, the software copies the translation from the translation memory. Where there are changes, the translator does the translation, with the new translation being copied into the translation memory.

I think your client needs to talk to the translation vendor to see if the vendor uses translation memory. And discuss specifically what happens when changes and updates are made: what does the client need to provide? Is previously translated content translated again, and at the same cost? I would suggest that if the client's vendor does not use translation memory, then he should look to another vendor.

Van