On Wed, Jul 27, 2005 at 10:07:57AM -0500, Andy Lester wrote: > On Tue, Jul 26, 2005 at 06:38:00PM -0700, Michael G Schwern ([EMAIL > PROTECTED]) wrote: > > More importantly, make your source data as exact as possible so the maximum > > amount of information is available to the user. Case is information. > > My only concern was false information, such as X<Operators> instead of > X<operators>.
This is valid concern. I'd see it as: Proper nouns and terms where cApItAlIsaTiOn is significant really should be put into X<> as is. Everything else should be lower case. Likewise singular unless the plural is specifically needed. No abbreviations. (Or always be consistent with everything using exactly 1 abbreviation) This lets the search tool decide whether it wants to do case insensitive matching. Rather than giving it no choice. However, I suspect that with a small amount of interactive search and replace we can correct anything needed by a later change of policy on normalisation. So this is a bit of a bikeshed issue. Nicholas Clark
