1) Same as multilingual content. So like client needs a rotator, we make it with the module builder and allow them to use RelatedData to pick an image. So then in that Image they should be able to define different images for the culture and it should change automatically based on that. So in the one example the client had english text baked into the image, so in this case, they would need a second image to show in FR mode automatically without needing to link multiple images in. We would also like a fallback (like the rest of the CMS) so if there is no FR translation defined, it just uses the EN one...
2) No...you want to link content once and have the reliant "Media content" loaded for the locale if it is set.
The only thing I would like you to think about is the "Use the file from other translation" part. If the image is exactly the same I would not like SF to create a new "Copy" of the image, only when it's physically changed\replaced. Like I dont want to have 1000 EN images, only 2 needing FR versions, but the CMS copying everything to give me 1998 identical files.
Antoaneta Tsaneva said:
We are still looking for feedback on the wireframes provided in Kali's post: http://pmfsto.axshare.com/#p=specific_file_for_language_version
We are wondering what are the most used scenarios for multilingual media items?
- Do you always plan to have different image/file for each translation or you will reuse most of the images/files and will add a new file in some translations only?
- From your perspective, is there any difference in the scenarios for Images and Files?
It would be great if you can also share a specific use case/scenario you have for multilingual media items.
Thanks a lot in advance,