Your message dated Sun, 27 Jan 2013 18:59:13 +0000
with message-id <[email protected]>
and subject line Re: Bug#698918: Acknowledgement (bitlbee: sending umlauts via
oscar doesn't work -- receiving and other protocols work fine)
has caused the Debian Bug report #698918,
regarding bitlbee: sending umlauts via oscar doesn't work -- receiving and
other protocols work fine
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
698918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698918
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bitlbee
Version: 3.2-1
Severity: normal
Dear Maintainer,
Using bitlbee 3.2-1 and xchat 2.8.8-7.1 I encounter the following problem with
umlauts (ä, ö, ü, ß etc):
- receiving from jabber clients works fine
- sending to jabber clients works fine
- receiving from oscar clients works fine
- sending to oscar clients DOES NOT.
<me> do these show up correctly? ae: ä, oe: ö, ue: ü, sz: ß
<guy using jabber> they do. let's try the other way: ae: ä, oe: ö, ue: ü, sz: ß
<me> works
<me> do these show up correctly? ae: ä, oe: ö, ue: ü, sz: ß
<guy using icq> nope. show up as russian characters. "ae: д, oe: ц, ue: ь, sz:
Я"
<guy using icq> ae: ä, oe: ö, ue: ü, sz: ß
<me> yours show up correctly
bitlbee's charset is set to utf-8:
<me> set charset
<root> charset = `utf-8'
xchat is set to use utf-8 as well.
-- System Information:
Debian Release: 7.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bitlbee depends on:
ii bitlbee-common 3.2-1
ii debianutils 4.3.2
ii libc6 2.13-37
ii libevent-2.0-5 2.0.19-stable-3
ii libgcrypt11 1.5.0-3
ii libglib2.0-0 2.33.12+really2.32.4-3
ii libgnutls28 3.0.20-3
bitlbee recommends no packages.
bitlbee suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On 27-01-13 16:24, Tim Wiederhake wrote:
> Heisenbug.
>
> Didn't change anything, but now it works.
> Yesterday it did not.
>
Odd. FWIW charsets on OSCAR are a pain. Last time I touched it is ages
ago, it mostly works but it depends very much on which client is
listening on the other side.
I decided to give up and just not care about any protocol that can't
comprehend UTF-8.
Glad to see the combination's working again for you at least. Indeed
stuff in iso8859-1 shouldn't be a problem IIRC.
Wilmer v/d Gaast.
--
+-------- .''`. - -- ---+ + - -- --- ---- ----- ------+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net |
+--- -- - ` ---------------+ +------ ----- ---- --- -- - +
signature.asc
Description: OpenPGP digital signature
--- End Message ---
