Using only small format works fine. The only problem is the sms notification dialog. It shows the number. But when you tap View, the contact is found and SMS app link the sms to the right contact. So it avoids 2 numbers. Incoming calls are displayed correctly. But I don't think searching contact like Nokia is a good idea. Last 6 digits are not always different (I'm talking about swiss numbers. we are using 10 numbers. The 3 first for the zone. so there may be same numbers in different zones). Contacts are in a sqllite database. When a phone comes in, the iPhone just have to find the short and long version and do a query in the db. All phones are able to do that now, without cutting the phone number. Nokia did this because the phone, at that time, was not powerful enough to do long queries.

Originally Posted by jacoch

Using only small format works fine. The only problem is the sms notification dialog. It shows the number. But when you tap View, the contact is found and SMS app link the sms to the right contact. So it avoids 2 numbers. Incoming calls are displayed correctly. But I don't think searching contact like Nokia is a good idea. Last 6 digits are not always different (I'm talking about swiss numbers. we are using 10 numbers. The 3 first for the zone. so there may be same numbers in different zones). Contacts are in a sqllite database. When a phone comes in, the iPhone just have to find the short and long version and do a query in the db. All phones are able to do that now, without cutting the phone number. Nokia did this because the phone, at that time, was not powerful enough to do long queries.

LAST (ie trailing) 6 digits won't even involve area codes... what are you talking about???

and there is literally a 1 in 1,000,000 chance that someone else ringing you is going to incorrectly match an entry in your phone book... even so what's the problem if it does happen??

Just changed the format to Australian. Thanks alot!

Originally Posted by Dell

Just changed the format to Australian. Thanks alot!

Hey mate can you tell me what you did to do this? and if they show correctly for both calls and when you rcv. sms?

Originally Posted by joe_hensonn

LAST (ie trailing) 6 digits won't even involve area codes... what are you talking about???

and there is literally a 1 in 1,000,000 chance that someone else ringing you is going to incorrectly match an entry in your phone book... even so what's the problem if it does happen??

I'm saying here the phone format is xxx yyy yy yy. xxx is the area. So if you check only the 6 last digits, you may miss numbers. Sure chances are quite small to have two in the address book. But if something needs to be written, why use a workaround used by Nokia some years ago because of phones with slow processors and capacity, when our iphone stores contacts in a sqllite db that could be queried very quickly and searching for the phone numbers without cutting it.

it should be ok for sms but no workaround for calls yet

Originally Posted by RVN84

it should be ok for sms but no workaround for calls yet

For calls you just need to put every number twice, once with +internationalprefix-local and once only local.

Cheers

Ben

I have tried hard to edit a plist file with Windows without any success. Even with the website provided from Chinaet, I still don't understand how to do it .

Anyone can help, pleeeeeeease.
Many, Many Thanks in advance.

Originally Posted by jacoch

I'm saying here the phone format is xxx yyy yy yy. xxx is the area. So if you check only the 6 last digits, you may miss numbers. Sure chances are quite small to have two in the address book. But if something needs to be written, why use a workaround used by Nokia some years ago because of phones with slow processors and capacity, when our iphone stores contacts in a sqllite db that could be queried very quickly and searching for the phone numbers without cutting it.

i think 8 digits would be fine.. remember it's a factor of 10 for each additional digit.

anyway i think you miss my point slightly.

the algo would roughly be:

1. read CID from incoming call
2. truncate string to LAST 8 digits
3. look for truncated string in phone book
4. if found, display name
5. if not found, display CID only.

the only fault of this method would be if someone NOT in your phonebook calls you and the 8 digits of their number matches someone in your address book. i think this is a pretty remote chance.

i played around with my nokia some time ago and i found that if you have 2 numbers recorded with same last 6 digits it will display the first one you created.

in any case someone needs to find and reverse eng the application on the iphone to use this or any method. you would also have to program that app to deal with the wide range of number formats in the plist files.

Don't get the factore of 10. Doing SELECT * FROM contacts WHERE (mobile = 'shortnum') OR (mobile = 'longnum') won't be much longer than searching for a single num that have been cut to 8 chars. And you're sure you find exactly what you are searching for.