[Hippo-cms7-user] URL name vs document name
Frank van Lankvelt
f.vanlankvelt at onehippo.com
Wed Feb 10 16:12:52 CET 2010
well, the node-name-codec is only reponsible for creating valid jcr node
names. It shouldn't need to know of all possible uses of the node. So I'm
pointing my finger at the HST...
Actually, I don't think this is a bad workaround at all. You'll get two
names; one ultra-safe name that will go through any codec, unharmed. And
the original, full name that the user provided. (you were going to store
that in the hippo:translated mixin on the handle, right?)
Note that your original request was for encoding diacritics; those are
actually allowed in URLs. They need to be properly utf-8 encoded, which is
something that is clearly within the realm of the HST.
On Wed, Feb 10, 2010 at 3:53 PM, Jasha Joachimsthal <
j.joachimsthal at onehippo.com> wrote:
> Actually it's a workaround. Either NodeNameCodec or the HST should handle
> documents with a '?' in the name better so they won't end up in the URL.
> On 10 February 2010 15:47, Frank van Lankvelt <f.vanlankvelt at onehippo.com>wrote:
>> it is. There is even an API to retrieve an encoder, so that one can plug
>> in encoders in at runtime, but I wouldn't think that this is necessary for
>> an importer ;-)
>> cheers, Frank
>> On Wed, Feb 10, 2010 at 3:34 PM, Arje Cahn <a.cahn at onehippo.com> wrote:
>>> > You can use the UriEncoding
>>> > String encoded
>>> > = StringCodecFactory.UriEncoding.encode("string-to-be-encoded");
>>> Is this the "Clean URL" functionality that Berry has worked on, or
>>> something else?
>>> Hippo-cms7-user mailing list and forums
>> Hippo-cms7-user mailing list and forums
> Hippo-cms7-user mailing list and forums
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Hippo-cms7-user