--- Dom Lachowicz <[EMAIL PROTECTED]> wrote: > New files. Contains 2 classes: > > UT_LocaleTransactor. Like the MutexAcquirer, it acts > to transact the > locale setting. so you might use it like this: > > UT_LocaleTransactor trans(LC_NUMERIC, "C"); > sprintf(str, "%f", args); > return; // locale implicitly rolled back
I believe the STL now has something kinda like this too. > ------------ > > UT_LangInfo. Has 2 meaningful constructors: > > UT_LangInfo() <-- gets your language from $LANG > UT_LangInfo(const char *lang) <-- get language from > passed string > > $LANG can be something like: > > "en", "en_US", "en_US.utf-8", "en.utf-8", "en-US", > "en-US.UTF-8" Does it actually come straight from $LANG or does it come from the internally cached values parsed from $LANG at program initialization? I ask this because the Windows code acts in an equivalent manner but of course has no $LANG variable. What does this new code do on a Windows (or other) system? > There are 6 methods: > hasLanguageField, getLanguage > hasTerritoryField, getTerritory > hasEncodingField, getEncoding Also remember that the Unix locale can have one more field, often in practice it tends to be "@euro" where "@" is the field separator and "euro" is the "variant". This field is a bit vague though ): Another thing is that the encoding field does not tell us everything we need to know about the encodings needed on any particular system. Specifically the GUI can use a different encoding and on some non-Unix but Unix-like systems, the filesystem may also use UTF-8 I believe. > I hope to use this class in order to help sanitize > the strings mess, the spell checking mess, the > system.profile mess, the help files mess, among > other things. Good luck! Andrew. > Dom > ===== http://linguaphile.sourceforge.net/cgi-bin/translator.pl http://www.abisource.com __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com
