Enhance Replicator/Bard Localization

[aerni]

As of now, Replicator and Bard fields can only be localized at the top-level. It would be totally awesome to be able to configure localization on set fields instead. I'm running into this issue on every multi-site. I'm aware that this probably means a major refactor of how multi-sites work.

[jasonvarga]

One big hurdle I see with this is how to store a single nested localized field's value.

We could probably give each Replicator/Bard/Grid set/row an ID, then the localized version could reference that somehow. I still don't really know what that would look like in YAML. Maybe something like this?

replicator:
  -
    id: 123
    type: quote
    quote_text: Hello!
    quote_author: John Smith
  -
    id: 456
    type: photo
    image: foo.jpg

replicator:
  123:
    quote_text: Bonjour!

[JorisOrangeStudio]

One big hurdle I see with this is how to store a single nested localized field's value.

We could probably give each Replicator/Bard/Grid set/row an ID, then the localized version could reference that somehow. I still don't really know what that would look like in YAML. Maybe something like this?

Is this feature still being considered for future versions? Since each set already has unique IDs (right?), it would be great to know if there are any planned updates or improvements related to this. Thanks!

[JoeriE]

Would love to see this too!

[matrad]

Also for us this would be great.

All pages are buolt with Blocks (replicator sets) and each field has one or more fields what should not be translated (like images, icons).

This would be great if we can set this fields in the blueptint within the set to not translated.

Currently we need to change the image on 4 sites if we want to change it and we have 4 languages.