Try our conversational search powered by Generative AI!
AI OnAI Off
Localization of MediaData
Thanks for bringing this up, I'm glad you found the workaround for now. Would you mainly want to translate the metadata related to a media item? Or do you also see a need to store language specific file variations?
Sep 07, 2016 18:19
I'm mainly interested in translating the properties. Haven't yet needed to have a language version of the file itself.
Sep 07, 2016 18:38
Same goes for me, so far we've only had the wish to translate the metadata related to the media item.
Sep 08, 2016 8:55
Physical file per language (with fallback to master) would be preferred as well... We have been asked to provide different images (usually for background color) for different cultures.
Sep 08, 2016 9:51
+1 primarily for localizing the properties.
Grzegorz does it nicely here: https://gregwiechec.com/2015/07/localizable-media-assets/ , but additional code is required for migrating existing images from "Invariant" culture to an enabled master language.
Jun 02, 2017 19:33
This thread is locked and should be used for reference only.
Please implement a way to localize properties on MediaData objects. The documentation seems to support it at the time of this writing (http://world.episerver.com/documentation/Items/Developers-Guide/Episerver-CMS/9/Content/Assets-and-media/Media-types-and-templates/) but apparently this is incorrect and the suggested way to solve this is to do the workaround presented here: http://www.patrickvankleef.com/2014/06/16/use-culture-specific-mediadata-properties/.
Would be nice to have this feature built into the product, or at least (until fixed :-)) clearly stated somewhere that this is not possible.
Best regards
Martin