Thanks Scott.
That looks interesting, but I'm not sure that I fully understand the result of translating an assetNode. Does the node in the DAM get translated? If that's the case, does the origin page now point to a translated Asset?
For example, if I have an image set with dc:title and dc:description referenced by an Image component in /content/geometrixx/en and I translate to /content/geometrixx/fr will the alt attribute now be French everywhere?
Unfortunately, I'm still working with 5.6.1, so I can't test it out.
Even though we're able to set jcr:title and jcr:description for each component, this loses its appeal as soon as you have the same image used on two different pages.
One idea that I've considered is creating an Asset Editor-like page for each region, so all of the original files can stay in the DAM, but translatable properties will be centralized per Asset. Afterwards all image components would reference the Asset Editor path, which in turn references the DAM.
Can anyone provide a "high level" overview of best practices when it comes to localization and asset Metadata? The original question on Stack Overflow still stands: http://stackoverflow.com/questions/30738226/translating-image-metadata
Thanks!
