apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe Jr." <wr...@rowe-clan.net>
Subject i18n codepage guidance needed
Date Tue, 12 Apr 2011 16:29:45 GMT
I have one dev question for my apr_fnmatch() refactoring

Today we lowercase the two characters (and don't support case-insensitive
range matches at all, I won't change this apr-specific quirk).  But IIRC
there are language with multiple lower case representations of the same
upper case character, but never (or at least, rarely) visa versa?

Shouldn't we upcase both the text and match chars, instead, to better
support non-ASCII locales?  (Obviously, this ignores utf-8 issues, and
I'm not going to enable MBCS in this next release, but will at least make
it possible to enhance for MBCS later on, without changing fn prototypes).

View raw message