Hi, Unless someone gives a valid reason why not to, I'm going to merge a change which'll turn the Translations selection into "Default Encoding" (which'll allow selecting the default encoding to use for new users) in the Options, and effectively remove support for the translators in the Qt GUI.
Reasons for change to the new Encodings feature: 1. Allows you to choose a different encoding for different contacts, turning licq into a true multilingual ICQ client (unlike Windows ICQ :-) 2. Integrates very well with Qt's internationalization features (especially important for complex scripts like Hebrew and Arabic) -- since the text is converted to Unicode, instead of from one 8bit encoding to another 8bit encoding. 3. Provides support for many different encodings (including the encodings used on Windows machines, which are very important for ICQ interoperatibility) which cover all languages Qt can possibly display (quite a lot of languages in Qt 3.0). 4. You get all the functionality the old "translators" provided (if not -- tell me what's missing!) Anyone has reasons against the switch? Something more constructive than "old users are used to it" please; I hold the opinion that as time passes (and new versions are released) we _are_ allowed to throw away old features for sake of newer better-implemented features. Keep in mind that those changes would only go into 1.2, which is a version jump. _______________________________________________________________ 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
