Localization
Most custom skin implementations will require adding new items to language resources. Base resources, including language files, are not permitted to be modified, so custom skins will require their own language resources.
The first step in customizing skins would be to copy language resources from the base skin into your custom skin. These language resources should become your master language resources and be maintained across releases and as your skin evolves. In cases where you are using multiple skins, or a deep hierarchy, only one skin should contain the master language resources. By always updating and only using a single set of master language resources, consistency can be maintained across the entire SDL LiveContent Reach implementation.
After any SDL LiveContent Reach upgrade, Copy/Merge Language should be run on the master language resources and the corresponding base skin's resources to determine if new keys have been defined and whether they should be added to their masters or ignored as unnecessary in the custom skins.
These methods require the least amount of work and the lowest level of complexity in maintaining the SDL LiveContent Reach implementation consistency across all the languages your customers require.