You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@tapestry.apache.org by Juan Alvarez <ja...@fluidsignal.com> on 2003/03/06 12:57:04 UTC

Central localized strings

I have following situation:

I have in the same package:

RegionFields <-- component
RegionSelector <-- component
RegionMain <-- page
RegionDelete <-- page
RegionUpdate <-- page
RegionCreate <-- page

With the following design of localization, if i want to localize all the
package i need one .properties per idiom per element above.

Reading in the source code of the DefaultStringsSource i note the
following line:

  String specificationPath =
  component.getSpecification().getSpecificationResourcePath();

So i think is good idea add to DTD of component and classes the option
to parametrice the resource bundle of one page or component, in this way
a set of related components and pages can have centralized all of his
localization strings.

Oviously do an implementation of IComponentStringsSource is other option.

-- 
Juan Alvarez		                    Fluidsignal Group S.A.
mailto:jalvarez@fluidsignal.com        http://www.fluidsignal.com/
Key fingerprint: 15C4 0986 A174 862A B607 8EEA 934F 8649 07E2 EA40