I noticed the translation framework will create a new copy of the original content under the target language folder. So my data size increases by whatever size the original content was every time I use the translation framework to add a new language. Even though all languages use the same binary file and it's only the metadata that gets translated, the translation framework makes a new copy of the binary for each of the translated languages.
This is not a problem when the size of the original content is small, but when you are dealing with petabytes, adding a few more petabytes every time a new language is added is expensive.
I know in some other systems, when dealing with multilingual asset metadata, the binary is unique and it's only the metadata that gets translated.
My question to you guys is, what are the reasons why AEM needs/wants to create a copy of the asset binaries every time a new language is added?
Thanks in advance for all your help.
Below are the steps confirmed by the Engineering team to manage Asset metadata translation without impacting Repository size.