Hi Isomorphic,
I'm using current 6.1p with fmt-tag DataSource localization for .ds.xml (and .type.xml) files for servercode and fieldnames and GWT permutation localization for the client side.
This all works very well.
Now as our product targets different industries with slightly different terminology, the default column names and lables don't always fit perfectly.
Here I build a way to "overwrite" the properties from client side GWT permutations with customized DB content.
Now the same is needed for column names as those also don't always fit the default name. Right now I have an extra branch with hardcoded changes for the one customer that requested this first. Of course this is not a real solution.
Could you support a new attribute within the
in the .ds.xml header, that specifies by default the class you use for this:
I'd then subclass that class, @override the method and do a "if (translated in DB) return translation; else return super(...);".
This way, DataSourceLoader would then return my default strings, or, if customized, the customer-provided strings.
Thank you & Best regards
Blama
I'm using current 6.1p with fmt-tag DataSource localization for .ds.xml (and .type.xml) files for servercode and fieldnames and GWT permutation localization for the client side.
This all works very well.
Now as our product targets different industries with slightly different terminology, the default column names and lables don't always fit perfectly.
Here I build a way to "overwrite" the properties from client side GWT permutations with customized DB content.
Now the same is needed for column names as those also don't always fit the default name. Right now I have an extra branch with hardcoded changes for the one customer that requested this first. Of course this is not a real solution.
Could you support a new attribute within the
<fmt:bundle basename="com.isomorphic.test.i18n" />
"Note: The tags we use for internationalizing Smart GWT XML files look like standard JSTL tags; this is intentional, simply because developers are familiar with JSTL. However, the tags are being processed by Smart GWT code, not JSTL, so only the specific tags documented here are supported."
This way, DataSourceLoader would then return my default strings, or, if customized, the customer-provided strings.
Thank you & Best regards
Blama
Comment