FAQ

Заходи и выигрывай на этом сайте, бесплатно и без регистрации.

случка лабрадоров;регламентные ТО и ремонт на Мерседесе М-класса в Москве

Does mICQ support uploading of contacts to the server?

Partially. Read the documentation. It might not be able to change some things.

What do these symbols mean that are printed for each contact with the 'e', 'w', 'ee', 'ww' and 's' commands?

The symbol printed after the peer-to-peer protocol version with the 'ee' and 'ww' commands are connectivity flags:

  • '%': SSL-encrypted direct connection with contact established.
  • '&': direct connection with contact established.
  • '|': direct connection with contact failed.
  • ':': direct connection with contact is tried to establish.
  • '.': direct connection with contact closed.
  • '^': no direct connection, but IP address and port number known.
  • ' ': no direct connection possible.
The symbols printed with all commands are contact flags:
  • '+': alias entry, only with 'ww'
  • '#': temporary contact (i.e. UIN was mentioned, but not added to contact list), only with 'w' and 'ww'
  • '*': intimate: sees you when invisible
  • '-': hide: doesn't see you at any time
  • '^': ignore this contact
If none of the latter are applicable, '&', '|', ':', '.' as above are printed if applicable.

Does mICQ support double wide (i.e. Japanese, Chinese) characters?

Mostly: line breaks will be wrong. Editing on the command line should be fine.

Why do messages to and from some contacts are noted with '«««' and '»»»', while for some others '<<<' and '>>>' are used?

The style of those indicates the transport mechanism used. '<<<' and '>>>' are non-acknowledged messages through the server, '«<<' and '>>»' are acknowledged messages through the server, '«««' and '»»»' are acknowledged messages via a direct connection, and finally '»%»' and '«%«' acknowledged messages via an SSL-encrypted direct connection.

How do I report bugs?

You first make sure that you have the latest and greatest version of mICQ - the bug might have already been fixed. Also check the mailing list archive if it's mentioned there, and, of course, this FAQ. You might also check the version in CVS, or this page in English. If you still think you've found a new bug, please report it to me, and please report as much detail about your setup as possible. If you can provide a fix, that would be appreciated very much, but, because of the speed mICQ evolves, if possible create a diff against the current CVS.

Are there any known bugs in mICQ 0.5.1?

Yes, there are.