Other Options for Localization

In some cases, different localizations of the a component will be very similar, perhaps having only one or two small snippets of text that is different. In those cases, it may be easier on the developer to not localize the HTML template, but to replace the variant text with an Insert component.

The page can read a localized strings file (a .properties file) to get appropriate localized text. This saves the bother of maintaining multiple HTML templates. This is the same approach taken by the Apache Struts framework.

All components on a page share the single locale for the page, but each performs its own search for its HTML template. This means that some components may not have to be localized, if they never contain any static HTML text. This is sometimes the case for reusable components, even navigational borders.