Alexander Klimetschek wrote:
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.
Hmm, yes and no :) Now, these characters are valid from the jcr pov (at
least I think they are), so there is no need to convert them.
On the other hand it might be usefull to create "pretty names" or web
friendly names; but I'm not sure if this is the task of Sling to do
this. We *could* create such a hook, but as this is only used in the
case of the post servlet and not if nodes are created through any other
way, I tend to leave this to the client code calling the post servlet.
Carsten
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?
--
Carsten Ziegeler
[EMAIL PROTECTED]
