pidgin/pidgin
merge of '86051d2c303f072b84abd0c006f6ca4e7bd9cea7'
and 'd698a51b3942fded75c51a242afa92541254da2d'
and 'd698a51b3942fded75c51a242afa92541254da2d'
# (01時52分58秒) wing: hmm. does "screen name" mean "user name" now, or has it actually always meant "user name"?
# (02時09分45秒) KingAnt: wing: They're the same thing. If you're unhappy with the change please email the gaim-devel mailing list. (I'm unhappy with the change.)
# NOTE (01時35分37秒) wabz: Anyway, I think the concept is more important than the literal translation - you use "Toggle Tag" on the currently selected buddy, then select a group/contact and hit "Place Tagged", and the buddy is moved
# NOTE in jabber each user has control over both who is in his/her buddy list and who has him/her in that other person's buddy list
# NOTE ie each "subscription" represents the fact that either you send status notifications to someone, or that you recieve them, or both
# NOTE thus "from" means you only recieve status notification, "to" means you only send status notification and "both" is thus obviously that you both send and recieve status notification
# NOTE marv: marv: in the room list stuff? yeah it's a user created room as opposed to an official room
# NOTE (21:29:48) KingAnt: wing: The AIM protocol allows people to advertise the song their currently listening to as part of their status
# NOTE (01:25:44) LSchiere: if you take the dictionary definition, its more or less the same as "sick"
# NOTE marv: marv: in the room list stuff? yeah it's a user created room as opposed to an official room
# NOTE (15:05:28) aatharuv: wing: A class is basically a high level chat. Any message sent to a class will also have "instance", and "recipient" parameters, which control who gets it. If someone "subscribes" to only a particular instance of the class, they'll only get messages sent to the specific class and instance, whereas someone who subs to all the instances of the class, instance "*", will get any message to the class.
# NOTE (15:11:31) aatharuv: The "recipient" field also controls who gets a message. if the recipient is "", then anyone subbed to said class and instance will get the message, otherwise it will only be received by the person with that "username". This allows IM's in zephyr to be a special case of chats
# NOTE (14:46:12) aatharuv: wing: So all zephyrs get sent to a triplet <class,instance,recipient> . "message" is the default class that zephyrs go to, and "personal" is the default instance.
# TODO Untranslated - This will need to be translated (NOT transliterated) for Chinese, but that'd be too much work
#. * "MIME Type" (I have no clue how that would be a desktop item) and "Comment"... nothing we can really
#. * send. The only logical one is "Application," but do we really want to send a binary and nothing else?
# TODO Untranslated - This will need to be translated (NOT transliterated) for Chinese, but that'd be too much work
#. Translators: "New conversations" should match the text in the preferences dialog and "By conversation count" should be the same text used above
# NOTE (00:38:50) LSchiere: wing: the statement quotes only makes sense in terms of the realization that there is no inherent correlation between im of any type and email
# NOTE (00:39:19) LSchiere: wing: apparently when adding a contact to your address book, if you fill in the screenname/im field, it is auto adding it to your list.