On 3/22/07, Stefan Haun <[EMAIL PROTECTED]> wrote:
To achieve this, I'll do the following: - submit a patch for the history reading/writing mechanism to use UTF-8 only
Sounds good.
- code a script which converts the existing history into UTF-8, dependent on the per-user encoding settings
Ahh yes, we can try and use this. There will be some encoding failures for sure. But that just means that the user can't even see the history unless they fiddle with the encoding settings anyways...
Sometime this month, I hope.
I can whip up an upgrade script for this on my lunch break some time as well if you want. Been meaning to work on the new API documents as well. I guess I have some stuff to keep me busy at lunch this week ;) Jon -- ________________________________________________________ Jon Keating ICQ: 16325723 [EMAIL PROTECTED] MSN: [EMAIL PROTECTED] http://www.licq.org GPG: 2290A71F http://www.thejon.org HOME: Minamiashigara, Japan
