Opened at 2008-01-12T12:16:03Z
Closed at 2008-01-13T00:17:17Z
#348 closed defect (fixed)
bitlbee not connecting if charset == iso-8859-15 and Realname contains a "umlaut"
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | 1.2 |
| Component: | BitlBee | Version: | devel |
| Keywords: | Cc: | ||
| IRC client+version: | Client-independent | Operating System: | Linux |
| OS version/distro: |
Description
When an Umlaut is set in realname when connecting to bitlbee, then the client is stuck.
Trafficdump:
:bitlbee.gladeguard.org NOTICE AUTH :BitlBee-IRCd initialized, please go on NICK Bonsi USER knoppix knoppix vpn.gladeguard.org :Jens S.lwald
Hexdump:
00000000 4e 49 43 4b 20 42 6f 6e 73 69 0d 0a 55 53 45 52 NICK Bon si..USER 00000010 20 6b 6e 6f 70 70 69 78 20 6b 6e 6f 70 70 69 78 knoppix knoppix 00000020 20 76 70 6e 2e 67 6c 61 64 65 67 75 61 72 64 2e vpn.gla deguard. 00000030 6f 72 67 20 3a 4a 65 6e 73 20 53 fc 6c 77 61 6c org :Jen s S.lwal 00000040 64 0d 0a d..
When issuing a "/quote user" without the umlaut, everything works fine.
(Everything is fine, if i choose uft-8 as Charset)
Client: xchat 2.8.4-1 Windows 6.0 [i686/2,39GHz] Server: bitlbee-bzr-300. bitlbee.gladeguard.org :Linux/x86_64
Attachments (0)
Change History (1)
comment:1 Changed at 2008-01-13T00:17:17Z by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
changeset:devel,302 should fix this problem. Thanks a lot for finding this!