One of our content-editors noticed that the focus-point of images has to be set individually for every language. This can become quite cumbersome for a setup with several languagesā¦ we also donāt see the benefit of having an individual focus-point for every language.
Is this something that could be toggled? Eg. make the focal-point translatable or opt-out of translation?
Any advice is highly welcome
Hello @tools1
The best way to do so would be to make the Asset field that the image is in not localised, that way it will maintain the focal points across all locales.
Hi @m.finamor
I have to come back to this problem, since itās only partially solved.
For āModelsā itās easy to disable localisation on individual image-fields. However, we have Blocks that contain images, as well as text-content (which should be translatable).
When we add a āModular Contentā field on one of our models (with enabled localisation for the modular content), then the images will also become translatable, resulting in the problem with the ātranslatedā focal-point.
As a lot of our āpage-contentā is based on modular blocks, the problem shows up quite often.
Hello once again @tools1
I see, however there are only a couple solutions i see for your use case:
For now the immediate option seems to be only the first one, or to set the focal point on all locales manually unfortunately
Hi @m.finamor
Thanks for your swift reply.
We have content-blocks that need to have image and text fields in the same block, so separating them wonāt work. But since the ālocaliseā Option is on the āModular Contentā field, this solution wonāt work anyway, right? Since localising a Modular-Content field results in all allowed blocks to be localised.
We just use a single Modular-Content field and the editors can then create the different content-blocks there.
Having localisation on the block-level would be better in this case. So Iām also giving a 
to this feature-request 
@tools1 , yes, sorry, i meant splitting them in two different blocks, and then splitting those blocks usage in two different modular content fields, e.g: one non localized modular content field called āImagesā for non localized content assets, and one localized modular content field called āTextsā with the text fields
- Adding on our end a way to localize image fields but mantain focous points across locales (which seems very counter intuitive for the majority of other use-cases)
Hi @m.finamor weāve run into the same problem where we use the same assets on multiple locales (20+) with multiple device variations (mobile/desktop). Its a massive amount of manual work, and theres no value inputs so every locale will get a slightly off-set focal point because you need to click an image in the exact same location.
The expected behaviour is for a focal point to behave like a default value in the Media area, the same as alt texts/captions: Type something to overwrite the default value for this asset.
The current behaviour seems more counter intuitive.
Additional request if we were to do this manually is to have numerical input fields in addition to the āClick on the imageā interface, so we can at least have the exact same Focal point between locales.
I just figured out focal point is per locale.
That is non intuitive. Would also advocate for neutral focal point.
Hey @david.desloovere can you open a feature request for this right here: ā Feature requests - DatoCMS community so we can check the community opinion on this subject? Thank you!