A minor, but very helpful addition:
For languages with Umlaute and other special characters, it would be
cool to support translating them into the nearest normal letter
instead of "_". For example, "รค" -> "ae" etc.
A simple way would be to provide a (configurable) map for looking up
the translated variant of the character. If nothing is found in the
map, "_" will be used as default?
Question is how to make the map extensible, so that new translations
can be easily added once someone comes up with a new one (and sling
core developers don't have to bother with those additions ;-). Maybe
through an OSGi service? Or could it be stored in the JCR repository?
Alex
Am 14.04.2008 um 14:19 schrieb Carsten Ziegeler:
Hi,
I'm currently working on SLING-354 [1]
My idea is to rename the parameter as discussed to "nameHint" with
the semantics that this hint is used as specified if it is a valid
node name. Invalid characters will be replaced with a "_".
If a node with the name already exists, a number is prefixed to the
node name (like it is currently done).
Now, there is already a filtering for node names if the special
properties like jcr:title, name etc. are used. But this filtering is
much more strikter: it always creates a lower case name and replaces
valid characters (like spaces etc.) as well.
I think we should have the same behaviour when it comes to filtering
and think we should only replace invalid characters.
WDYT?
Regards
Carsten
[1] https://issues.apache.org/jira/browse/SLING-354
--
Carsten Ziegeler
[EMAIL PROTECTED]
--
Alexander Klimetschek
[EMAIL PROTECTED]
>> Day JCR Cup 08 | Win a MacBook Pro: http://dev.day.com/ <<
