Return-Path: X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4D376D1E3 for ; Thu, 11 Oct 2012 13:13:13 +0000 (UTC) Received: (qmail 68475 invoked by uid 500); 11 Oct 2012 13:13:12 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 67945 invoked by uid 500); 11 Oct 2012 13:13:06 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 67892 invoked by uid 99); 11 Oct 2012 13:13:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Oct 2012 13:13:03 +0000 Date: Thu, 11 Oct 2012 13:13:03 +0000 (UTC) From: =?utf-8?Q?C=C3=A9dric_Damioli_=28JIRA=29?= To: dev@jackrabbit.apache.org Message-ID: <1992312700.26137.1349961183765.JavaMail.jiratomcat@arcas> In-Reply-To: <695708416.21096.1349892063794.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (JCR-3443) Normalize String properties when ordering query results MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/JCR-3443?page=3Dcom.atlassian.j= ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D134741= 26#comment-13474126 ]=20 C=C3=A9dric Damioli commented on JCR-3443: ------------------------------------- a) Do you suggest someting like "rep:normalize" ? b) I did not actually tried to implement a collation algorithm, which certa= inly depends on locales, but instead a normalization algorithm (http://www.= unicode.org/reports/tr15/) which do not depend on locales. I could have implement it using java.text.Normalizer.normalize(), followed = by the removal of non ASCII-characters, but this is roughly equivalent to t= he more easier Unicode-to-ASCII method I found in the Lucene code. =20 > Normalize String properties when ordering query results > ------------------------------------------------------- > > Key: JCR-3443 > URL: https://issues.apache.org/jira/browse/JCR-3443 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: jackrabbit-core, query > Reporter: C=C3=A9dric Damioli > Attachments: normalize.patch > > > Properties containing non-ASCII characters are not well collated in query= results > There's only two allowed functions so far in XPath (fn:lower-case and fn:= upper-case). There exists the equivalent LOWER and UPPER in SQL > I propose to add a fn:normalize (resp NORMALIZE) function giving expected= results -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira