Branch: refs/heads/1.5-stable
Home: https://github.com/licq-im/licq
Commit: 536381f0fa6a0c9e6c567f36836746b23a988d66
https://github.com/licq-im/licq/commit/536381f0fa6a0c9e6c567f36836746b23a988d66
Author: Anders Olofsson <[email protected]>
Date: 2011-07-21 (Thu, 21 Jul 2011)
Changed paths:
M licq/src/buffer.cpp
Log Message:
-----------
Fix string handling in Buffer to null terminate
Commit: 599f94fbb42a36787be831476032d23e5de55891
https://github.com/licq-im/licq/commit/599f94fbb42a36787be831476032d23e5de55891
Author: Anders Olofsson <[email protected]>
Date: 2011-07-21 (Thu, 21 Jul 2011)
Changed paths:
M licq/include/licq/icqdefines.h
M licq/src/icq/icq.cpp
Log Message:
-----------
icq: Recognise UTF8 messages on channel 2
This solves problem with messages from Miranda being received with bad
encoding.
Solution is a quick solution based on how Miranda parses the messages.
Pidgin seems to not check at all and always assume it is UTF8 so the
extra check might not even be needed.
Commit: ca13659cda3d6c46fa32614bd722e9be13e7dfef
https://github.com/licq-im/licq/commit/ca13659cda3d6c46fa32614bd722e9be13e7dfef
Author: Anders Olofsson <[email protected]>
Date: 2011-07-21 (Thu, 21 Jul 2011)
Changed paths:
M licq/doc/CHANGELOG
M licq/src/icq/icq-tcp.cpp
Log Message:
-----------
icq: Always send non-ascii messages as UTF8
This is based on how Miranda and Pidgin sends their messages. If they
can send UTF8 always it's probably safe for us to do the same thing.
Also dropped the check if recipient is online for the same reason.
Compare: https://github.com/licq-im/licq/compare/3b71b8c...ca13659
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.