Return-Path: 
 <lucene-dev-return-999-qmlist-jakarta-archive-lucene-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-lucene-dev-archive@apache.org
Received: (qmail 49572 invoked from network); 11 Mar 2002 21:29:10 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 11 Mar 2002 21:29:10 -0000
Received: (qmail 20861 invoked by uid 97); 11 Mar 2002 21:29:05 -0000
Delivered-To: qmlist-jakarta-archive-lucene-dev@jakarta.apache.org
Received: (qmail 20801 invoked by uid 97); 11 Mar 2002 21:29:04 -0000
Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:lucene-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:lucene-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:lucene-dev-help@jakarta.apache.org>
List-Post: <mailto:lucene-dev@jakarta.apache.org>
List-Id: "Lucene Developers List" <lucene-dev.jakarta.apache.org>
Reply-To: "Lucene Developers List" <lucene-dev@jakarta.apache.org>
Delivered-To: mailing list lucene-dev@jakarta.apache.org
Received: (qmail 20746 invoked from network); 11 Mar 2002 21:29:03 -0000
content-class: urn:content-classes:message
Subject: RE: Normalization
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 11 Mar 2002 14:28:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: <E63F5ED34054F74DB951DC93B3045B120118770C@AZCPMAIL.infoimage.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Normalization
Thread-Index: AcHJQ0/a0+Eg5b1STCKaztdKYU0wsgAAFjtA
From: "Mark Tucker" <MTucker@infoimage.com>
To: "Lucene Developers List" <lucene-dev@jakarta.apache.org>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

You can't learn, if you don't ask the question.  Thanks for your =
response.

Mark

-----Original Message-----
From: Rodrigo Reyes [mailto:reyes@charabia.net]
Sent: Monday, March 11, 2002 2:26 PM
To: Lucene Developers List
Subject: Re: Normalization



 Well, choosing XML for such a description language has the following
drawbacks:

 * hardly legible. Having one rule per line is really nice. I =
appreciated it
writing the french normalizer.

 * it does not solve all the parsing problems.
    - either you have to specify everything as elements or attributes, =
and
it's painful :
         <leftContext><range =
value=3D"aeiou"/>er<range=3D"tr"/></leftContext>
         <rightContext>er<boundary/></leftContext>
    - either you have a write a parser anyway to parse the content of =
the
elements:

         <rightContext>[aeiou]r$</leftContext>
        and therefore write a parse for the content of the xml-parsed
content.


 Rodrigo
----- Original Message -----
From: "Mark Tucker" <MTucker@infoimage.com>
To: "Lucene Developers List" <lucene-dev@jakarta.apache.org>
Sent: Monday, March 11, 2002 10:10 PM
Subject: RE: Normalization


> Why not use XML?
>
> <normalizer>
> <rule>
> <leftContext></leftContext>
> <rightContext></rightContext>
> <transformLetters></transformLetters>
> <replacementString></replacementString>
> </rule>
> <rule>
> <leftContext></leftContext>
> <rightContext></rightContext>
> <transformLetters></transformLetters>
> <replacementString></replacementString>
> </rule>
> </normalizer>
>
>
> There are some issues with the characters you use, but using XML might
make it easier to extend.
>
> Mark



--
To unsubscribe, e-mail:   =
<mailto:lucene-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: =
<mailto:lucene-dev-help@jakarta.apache.org>


--
To unsubscribe, e-mail:   <mailto:lucene-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:lucene-dev-help@jakarta.apache.org>