Feature Requests item #556766, was opened at 2002-05-16 09:37
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=354754&aid=556766&group_id=4754
Category: framework
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Howard Lewis Ship (hship)
Assigned to: Howard Lewis Ship (hship)
Summary: Improve localization support
Initial Comment:
Tapestry needs improved localization support.
Every component should have the option of localizing
messages using multiple HTML templates, or using a
property resource bundle (a set of
localized .properties files) (or a combination of the
above).
A new binding, for extracting a localized string from
the properties files would be useful. Example:
<component id="insertMessage" type="Insert">
<string-binding name="value"
property="a.message.key"/>
</component>
Note that the key is simply a key, not a property path.
IComponent should have additional methods for
obtaining a localized ResourceBundle for the component.
To be discussed:
Should there be an inheritance chain? If a component
does not have the specified key, should the search
continue in the containing component? Containing
page? Engine?
There may be some use to allowing access to these
using property bindings, i.e.,
<binding name="value" property-path="strings.
{a.message.key}"/>
Note the big change, use of a delimiter to identify a
key that contains dots.
Simple HTML:
This is going to occur often enough that I support
bending the rules for Tapestry HTML templates. I
would like HTML templates to look like:
<span property="a.message.key">Default Text</span>
This would act like a kind of macro, automatically
creating an object, or anonymous Insert, that
retrieves the specified key from the localized strings
and replaces the entire <span> tag with it. Again,
this would support WYSIWYG, since "Default Text" would
appear when the HTML producer is working on the
template.
This would look specifically for "span" tags with
a "property" attribute.
This would involve a change to HTML parser.
Note that under this scheme, the use of multiple HTML
templates would take on a very different usage, I
suspect: The ability to change L&F for a page based
on locale ... you'd use a different HTML template for,
say, Hebrew than for English, to reflect the
orientation difference (English is left to right,
Hebrew is right to left).
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=354754&aid=556766&group_id=4754
_______________________________________________________________
Hundreds of nodes, one monster rendering program.
Now that�s a super model! Visit http://clustering.foundries.sf.net/
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
