According to trolltech's QT docs, i.e. http://doc.trolltech.com/3.3/i18n-example.html#x1963 > QButtonGroup *bg = new QButtonGroup(4,Qt::Vertical,"Choose Locales",&dlg); > QString loc = QTextCodec::locale(); > for ( int i=0; qm[i]; i++ ) { > qmb[i] = new QCheckBox((const char*)qm[i],bg); > qmb[i]->setChecked( loc == qm[i] ); > }
and http://doc.trolltech.com/3.3/qtextcodec.html#locale > const char * QTextCodec::locale () [static] > Returns a string representing the current language and sublanguage, e.g. > "pt" for Portuguese, or "pt_br" for Portuguese/Brazil. twinkle is handling locale correctly. If anybody thinks, LC_MESSAGES should be regarded for GUI setup (which seems not absolutely clear to me, Gui is not msgs. Anyway...), maybe this is a bug to be filed against QT QTextCodec::locale(), not against twinkle. Or is there any different "best practice", that obsoletes the QT docs? If so, please give a pointer and i'm sure we will see what can be done. Bottom line: to me it seems this simply is *no* bug. For sure it's not a genuine twinkle bug. cheers jOERG -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
