Problem with buddy name

Daniel Atallah datallah at pidgin.im
Wed Oct 20 10:29:38 EDT 2010


On Wed, Oct 20, 2010 at 10:07, Wolfe, Rick G x28837
<Rick.Wolfe at broadridge.com> wrote:
> Protocol is "Sametime".  Does this answer your question?

Please reply to the support mailing list instead of to me directly.

Yeah, it is the answer I was looking for.

The simple answer is that Sametime support is maintained via patches -
none of the current developers have access to a sametime server, nor
are they knowledgeable about the protocol.

If there isn't already a ticket for this particular issue, you can
file a ticket at at http://d.pidgin.im/newticket.

-D

> -----Original Message-----
> From: daniel.atallah at gmail.com [mailto:daniel.atallah at gmail.com] On Behalf Of Daniel Atallah
> Sent: Wednesday, October 20, 2010 09:48
> To: Wolfe, Rick G x28837
> Cc: support at pidgin.im
> Subject: Re: Problem with buddy name
>
> On Wed, Oct 20, 2010 at 09:07, Wolfe, Rick G x28837
> <Rick.Wolfe at broadridge.com> wrote:
>> I've noticed for a long time that the buddy name gets truncated for certain
>> people.  I found the commonality to be the way the adminstrator assigned the
>> name.
>>
>>
>>
>> For instance: "Crane, Dave x28619,Crane,Crane,Crane" displays as "Dave
>> x28619" (truncated)
>>
>>           or: "Passes, Harvey,Passes" displays as "Harvey" (truncated)
>>
>>
>>
>>          but: Farley, Peter x23353 displays as "Farley, Peter x23353" (full
>> name).
>>
>>
>>
>> When I assign an alias name to display the full name, it displays the alias
>> until the next time I reconnect, then it goes back to the truncated name
>> again.
>
>
> Which protocol (AIM/Yahoo/MSN/XMPP/etc.) are you seeing this with?
>
> -D
> This message and any attachments are intended only for the use of the addressee and
> may contain information that is privileged and confidential. If the reader of the
> message is not the intended recipient or an authorized representative of the
> intended recipient, you are hereby notified that any dissemination of this
> communication is strictly prohibited. If you have received this communication in
> error, please notify us immediately by e-mail and delete the message and any
> attachments from your system.
>
>



More information about the Support mailing list