Find and localize terms inside edited content from a Live-copy replication without losing inheritance

[EduardoMa9]

Hi,

We have a question, about something our customer has asked but we do not know how to solve it (or if it can be solved) without full replication.

I explain: starting from a language-master, we are creating from it a live-copy to replicate it into different marketing zones (Spain, Mexico, Peru, …) and so all of these zones copied will keep the inheritance of components and content defined in the language-master. 

At now we are being asked that for some of these zones they want that some of the terms in use inside the content provided by the content creators to be “translated” or adapted for the specific vocabulary of the region they represent in the marketing zone (localization); for example,  if the content has the word “Master” in Spain, they want it to be displayed as “Maestría” in the Mexico zone, “Magisterio” in another, etc… 

The tricky point is that these terms would be anywhere inside the content of the page edited freely; by that we mean inside the different components that can be edited by the component editors: an editor can edit content and provide text freely, that is the content we want to modify (in an automatic way); but we want to perform this changes and keep at the same time the inheritance originally defined.

Is there any way we could achieve this? What would you recommend?

Many thanks in advance

[VishalKa5]

Hi @EduardoMa9 ,

You cannot safely change words inside Live Copy content without breaking inheritance if you edit the content itself.

Follow below steps:
Handle this as localization at render time, not as content changes.

How to do it:

• Keep one Language Master

• Create region-specific dictionaries (Spain, Mexico, Peru, etc.)

• Automatically replace specific terms when the page is rendered

  • Example:
    Master > Maestría (Mexico)
    Master > Magisterio (Peru)

Why this works:

• Inheritance is preserved

• No content duplication

• Editors write text normally

• Localization is automatic and scalable

Recommendation:
Use dictionary / i18n based word replacement in Sling Models or HTL during rendering.

Thanks,

Vishal 

[muskaanchandwani]

Hello @EduardoMa9 

Out-Of-The-Box :
MSM alone cannot do word‑level localization (like auto‑replacing “Master” => “Maestría”/“Magisterio”) while keeping the same field inherited; MSM works on nodes/properties, not on individual words.

If you break inheritance on a component/field to localize the wording, that field stops receiving updates from the language‑master on future rollouts.

Recommended approaches instead of raw text overrides:
1. Regional language masters with MSM
Have language-masters/es → MSM live copy to language-masters/es-latam (adjust vocabulary there), then roll out from es-latam to markets like mexico/es, peru/es.
Good when regions can share vocabulary.

2. Terminology dictionary + tokens (best pattern)
Authors use tokens like {{term.master-degree}} in text.
Each market has a dictionary mapping that token to “Master” / “Maestría” / “Magisterio”.
Components resolve tokens at render time based on the current site/locale.
Keeps MSM inheritance intact; only the dictionary varies per market.

3. Per‑component override fields
Split content into “global sentence” + “local term” field.
Configure MSM to not sync the local term property; sync only the global part.
Works when sentences are structured and predictable.

4. HTML search‑and‑replace filter (last resort)
Do runtime string replacement in rendered HTML per locale.
Fast to add but fragile and hard to maintain; only suitable as a temporary workaround.

So: no OOTB switch to get this behaviour; you need either a regional MSM layer or a dictionary/token approach to keep inheritance and vary terms per market.