On Tue, 24 Jan 2006, Brian Kirsch wrote:
Andi,
What do recommend doing in the case where a locale is not know for the text?
Email is a great example, in most cases no language (locale) headers are
supplied.
When no locale is supplied, the encoding supplied could be used for clues for
using a set of heuristics helping to 'guess' a locale. In the case of email,
for example, the domain of the sender may also provide a clue.
That guess may be better than nothing but not by much...
A good guess at this is important for full text indexing.
When sorting email addresses, however, I'd think that the Chandler user's
locale would prevail over the potential locale of the data being sorted.
Andi..
-Brian
Brian Kirsch - Email Framework Engineer
Open Source Applications Foundation
543 Howard St. 5th Floor
San Francisco, CA 94105
(415) 946-3056
http://www.osafoundation.org
Andi Vajda wrote:
On Tue, 24 Jan 2006, Brian Kirsch wrote:
One issue to remember, if we are sorting on the name of the user i.e.
Brian Kirsch <[EMAIL PROTECTED]> then the sort order will need to
be localized with PyICU.
Last year, I added a new index class called StringIndex. It understands
locale and uses PyICU's collator support for comparing strings.
Similarly, I realized recently that for full text indexing's sake, LOBs (at
least, if not all attributes) should also have a locale aspect so that when
full text indexing (and queries) are run, an analyzer that is appropriate
for the language of the locale is used to break up the text (or queries) in
tokens.
Andi..
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
