Hello How should collation be handled in multitasking, multilingual applications - in particular forking servers such as apache/mod_perl based web apps?
I can assume the following: 1) I'll know the preferred language via a RFC2616 language tag. 2) All data will be utf8 encoded Unicode. 3) The required language may differ for each request. I guess Unicode::Collate is the way to go, so can I simply have one Unicode::Collate instance per process using the default allkeys.txt table file? Will that give sensible results for most (all?) languages, or do I need to customise the collator on the fly when more 'exotic' (for want of a better word) languages are requested? Are there other reasons, such as size and/or performance issues, why the default allkeys.txt file may not be the way to go? I must stress that I'm ok with most aspects of i18n/l10n - it's specifically the correct use of Unicode::Collate in multitasking apps that I'm interested in. Suggestions would be welcome - even more so if they don't involve having to know the TR10 docs inside out! Cheers, -- Rich [EMAIL PROTECTED]
