Opened at 2010-02-02T16:08:26Z
Last modified at 2010-04-13T22:33:12Z
#561 new enhancement
feature requst: default oscar charset
| Reported by: | anonymous | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | BitlBee | Version: | 1.2.4 |
| Keywords: | Cc: | ||
| IRC client+version: | Client-independent | Operating System: | Public server |
| OS version/distro: |
Description
Problem: many popular icq clients ignore specs and don't bother convert messages into UTF-8, sending non-latin characters in native encoding. They also don't bother set correct flags for indicating the used charset. This requires the client to guess the charset used at the remote side.
Workaround: attached patch introduces another user-defined setting, "oscar_charset", which is "none" by default, which means unaltered behavior. If set to an encoding supported by iconv, all 8-bit data accepted through oscar protocol are converted into UTF8 using this encoding. It doesn't affect outcoming data.
Attachments (1)
Change History (2)
Changed at 2010-02-02T16:08:54Z by
| Attachment: | bitlbee.diff added |
|---|
comment:1 Changed at 2010-04-13T22:33:12Z by
Hello,
Thanks for the patch. Does this solve the full problem for you, as-in the outgoing messages from BitlBee are readable on their side in unicode, they just misbehave when sending stuff back?
I prefer to put protocol-specific settings inside the protocol modules so I'll modify your patch to do just that. Extra advantage is that, if necessary, you can have multiple OSCAR accounts with this setting set to different values, if such a thing would ever be necessary.
patch