[moved discussion to from turbine-user to turbine-dev]
Chris Kimpton <[EMAIL PROTECTED]> writes:
> As per the mail below, I am looking at ways to handle merging of
> localisation properties and had the idea of using sequences of
> resource bundles.
>
> Does this sound like the correct approach?
Yes, it does sound like the correct approach. I say this because I
already implemented it. ;P
> Is this something that would be acceptable in fulcrum/turbine 3? I
> could submit patches for this.
It's part of Fulcrum -- the bundles property is leveraged. It's quite
new, so if something is missing, broken, or not implemented to your
liking, please speak up.
> I see in fulcrum there is support for multiple resource bundles -
> perhaps a switch to allow this list to be used as a sequence of
> bundles for lookups?
It already is used as a sequence of bundles to iterate through during
a lookup. Could you provide an example of what you're trying to do so
I can see how it differs from what's there, and how I can make the
documentation more clear?
> Alternatively, via a new property which lists the bundle sequence to
> be used for default lookup processing.
The sequence that is used is as specified in the properties file, just
as any other search path (like the PATH environment variable looked
through for binaries).
> The getString methods would then follow the sequence of bundles to
> find a resource, as sketched out below.
If I'm understanding what you're saying, it already does this...how is
what you're proposing different?
Dan
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
