| Issue 10: | AIM Screennames case/space sensistive |
1 of 19
Next ›
|
| 1 person starred this issue and may be notified of changes. | Back to list |
What steps will reproduce the problem? 1. Have a contact with spaces/capitals in their screen name in Address Book, but all lowercase in Adium 2. Use the "Find Contacts in Adium but not in Address Book" feature 3. Contacts with different cases/spaces will show up as not in Address Book What is the expected output? What do you see instead? AIM allows the display of screen names with spaces and uppercase characters (basically ignores them), AdiumBook should do the same (at least for AIM screen names, I'm unsure of other protocol's treatment of spaces as capitals. Also, Adium DOES handle this correctly, so my contacts show up with their Address Book-imported names in my Adium buddy list. What version of the product are you using? On what operating system? 1.3.1 on OS X 10.5.2 NOTE: There's a chance that only capitals OR spaces are causing this issue, most of my contacts that had one had the other. |
|
,
Apr 04, 2008
I can confirm that capitalization alone causes this bug to show up. I'm unsure about spaces alone, but I'm willing to bet that they'll show up as different. Also, the contact can have capitalization in Adium but not in Address Book-- basically, anytime the names are not identical, AdiumBook considers them different despite the AIM protocol being space and name agnostic. This is with 1.3.1 on 10.5.2. |
|
,
Jul 29, 2008
Capitalization may not be the issue because AppleScript comparisons are ignore-case by default. I can't reproduce here the bug with capitalization alone. But yes, spaces are not handled well. The problem is that the definitive fix would make the address book searches too slow to be useful. We're hitting the AppleScript performance limits here. The new version 1.4 makes a step forward and fixes the AIM space problem at least for the "AB contacts not in Adium" report. This report should work fine regardless of the spaces. I'll try to address this issue again on a future release.
Status: Started
|
|
|
|