Received-SPF: none
 receiver=realpeople.com; client-ip=96.252.75.162; envelope-from=fred.stephenson@communication-unltd.com
Message-ID: <4C6EEC08.3020001@communication-unltd.com>
Date: Fri, 20 Aug 2010 22:56:40 +0200
From: Fred Step <fred.stephenson@communication-unltd.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Helix Discussion List <Helix-L@realpeople.com>
Subject: Re: [Hx] ASCII tile
References: <list-1550378@realpeople.com>
In-Reply-To: <list-1550378@realpeople.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Gib,
> I have a text field which creates a key field by defaulting to the 
> lower-case contents of first name and last name fields, e.g. John 
> Smith's record defaults to "johnsmith" (and no, two people may not 
> share the same first name/last name; one of them will have to 
> change).  The field may not contain anything but alphabetic 
> characters, e.g. no spaces, punctuation, accented characters.  
> Occasionally, the "first" or "last" name may be composed of a compound 
> name, e.g. Billy Jack or Betty Sue or van der Veer.  It's easy to 
> validate for no space using the Locate tile, thus catching this most 
> common type of invalid namekey entry.
>
> But how can I validate for any other special character?  Ideally, I'd 
> like to Locate any character whose ASCII value exceeds that of 'z' so 
> as to catch names like Renée Hörst, but a review of The Helix 
> Reference doesn't turn up that ASCII tile, thus suggesting it's just 
> not possible.  These occurrences are much less likely, so I guess we 
> can live with them, but is there a way to do this validation without 
> excessive overhead?  Cheers,

It's easy to catch characters outside the alphabet - can send a simple 
demo if necessary. BUT Renée will be considered as Renee.
I do believe Sven made a collection that could recognise those 
characters. Maybe it's amongst the gems on the FTP.

Cheers
Fred
> -- 
> Gib
>   Gib