On 3/22/07, Stefan Haun <[EMAIL PROTECTED]> wrote:
It seems, the files do not use a unique encoding, but store the message as-is, i.e. as it is sent by the peer. The other way around, if I change the encoding (say from ISO-8859-15 to UTF-8), the messages get stored in UTF-8, but the older messages are still in iso encoding. This becomes an issues when I review my history, because the encodings do not match.
I have to admit, while living in America I didn't give a second thought to character encodings and didn't really understand them, since they didn't affect me. So, that is the root of the problem. In Japan there are 3 major types of character encodings, so I've gotten used to the issues with them and wish I would have fixed this a long time ago in Licq.
- or convert the messages to an encoding used on the complete history
How about we save everything as UTF-8? The main issue that remains is what to do with an existing history file that is not in UTF-8. I'm sure some of the users out there have hugs history files in their own encoding.. I know I do.
I would create a patch on this, if it is still worth the work before Licq with the new API is released and which suggestion is better.
Sure, getting it fixed is a priority. But like I said, what do we do about converting existing files to UTF-8? The way I see it, we can assume the user's local encoding and try to convert it to UTF-8. Of course there will be some failures, but unless the user's do it manually that is to be expected, unfortunately. Jon -- ________________________________________________________ Jon Keating ICQ: 16325723 [EMAIL PROTECTED] MSN: [EMAIL PROTECTED] http://www.licq.org GPG: 2290A71F http://www.thejon.org HOME: Minamiashigara, Japan
