Hi, I'm proposing to make licq's backend guarantee returning UTF-8-encoded string values to the plugins in the 1.1.0 series. For that, I'll make licq link with libiconv and make the decoding and encoding right in the backend (e.g. SMSs are always transfered in UTF-8 over the net, contact messages would be decoded according to their UserEncoding setting). Additionally, I'll change the Qt GUI, so that it won't decode and encode text on its own with QTextCodec, but rather just interchange data with the backend in UTF-8 (which is trivial in Qt).
Do you guys have any objections? Benefits: - Unified i18n features between different plugins (licq, GTK). - Ability to have a single encoding in the History file / to choose in which encoding the History file should be saved. This seems to be very important for people who use system tools such as grep to operate on the history files. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Licq-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-devel
