Punctuating numbers in phonebook

Is there a way to punctuate numbers a Nokia handset which makes
them easier to read?

For example, rather than see 0012024621340 it would be nicer to see
something like this:

001 202 462 1340

But my Nokia wont take spaces in the number screen. What else can
be used? (Apart from w, p, *)

On Tue, 13 Apr 2004 19:46:39 +0100, Stefan
<stefan@ukmobileDELETETHISTEXT.fsworld.co.uk> wrote:

>Is there a way to punctuate numbers a Nokia handset which makes
>them easier to read?
>
>For example, rather than see 0012024621340 it would be nicer to see
>something like this:
>
> 001 202 462 1340
>
>But my Nokia wont take spaces in the number screen. What else can
>be used? (Apart from w, p, *)

Because number parsing is different all over the world it's unlikely
that you're going to find a phone that will do that in Europe or Asia.
Consider for instance numbers in the UK may be either 01xxx nx xx xx
or 020 nxxx xxxx in London, in France for Paris it might be 01 nx xx
xx xx, in Sydney it might be 02 nxxx xxxx. With all those different
ways to parse numbers it's no wonder that 900/1800 Mhz phones don't
automatically parse numbers. Nokia phones made for the North American
market automatically parse as North Americans are used to seeing
numbers i.e. nxx xxxx, nxx nxx xxxx, or 1 nxx nxx xxxx (n is any
number between 2 and 9 and x is any number) and will parse that way if
you use 462 1340, 202 462 1340 or 1 202 462 1340. However if you
deviate from that at all such as by making it +1 it will be all
smushed together such as if you had +1 202 462 1340 which looks on the
phone like +12024621340. Parsing goes out the window once you use a +
character on a North American phone.
- - - - - - - - - - - - - - - - - - - - - - - - - -
remove NONO from .NONOcom to reply

>>For example, rather than see 0012024621340 it would be nicer to see
>>something like this:
>>
>> 001 202 462 1340
>>
>>But my Nokia wont take spaces in the number screen. What else can
>>be used? (Apart from w, p, *)
>
> Because number parsing is different all over the world it's unlikely
> that you're going to find a phone that will do that in Europe or Asia.

ISTM that's a non-sequiteur : surely all that's required is a character
that's displayed as a space and is not transmitted to the dialer ?

There isn't even any particular need for there to be an industry-wide
standard so long as all phones stripped any non-numeric characters they
found in phone numbers from eg SIMs etc.

--
Boo

Boo <boo@spam_me_no_spam.net> wrote:

>>>For example, rather than see 0012024621340 it would be nicer
>>>to see something like this:
>>>
>>> 001 202 462 1340
>>>
>>>But my Nokia wont take spaces in the number screen. What
>>>else can be used? (Apart from w, p, *)
>>
>> Because number parsing is different all over the world it's
>> unlikely that you're going to find a phone that will do that
>> in Europe or Asia.
>
> ISTM that's a non-sequiteur : surely all that's required is a
> character that's displayed as a space and is not transmitted
> to the dialer ?
>
> There isn't even any particular need for there to be an
> industry-wide standard so long as all phones stripped any
> non-numeric characters they found in phone numbers from eg
> SIMs etc.
>


You got it right, Boo.

I think the guy who replied assumed that I want the phone to
cleverly use the breaks in the number. But all I want is a more
display of the number which is more intelligible.

"Stefan" <stefan@ukmobileDELETETHISTEXT.fsworld.co.uk> wrote in message
news:94CC76B048B1C547D@205.188.138.161...
| Boo <boo@spam_me_no_spam.net> wrote:
|
| >>>For example, rather than see 0012024621340 it would be nicer
| >>>to see something like this:
| >>>
| >>> 001 202 462 1340
| >>>
| >>>But my Nokia wont take spaces in the number screen. What
| >>>else can be used? (Apart from w, p, *)
| >>
| >> Because number parsing is different all over the world it's
| >> unlikely that you're going to find a phone that will do that
| >> in Europe or Asia.
| >
| > ISTM that's a non-sequiteur : surely all that's required is a
| > character that's displayed as a space and is not transmitted
| > to the dialer ?
| >
| > There isn't even any particular need for there to be an
| > industry-wide standard so long as all phones stripped any
| > non-numeric characters they found in phone numbers from eg
| > SIMs etc.
| >
|
|
| You got it right, Boo.
|
| I think the guy who replied assumed that I want the phone to
| cleverly use the breaks in the number. But all I want is a more
| display of the number which is more intelligible.

I totally agree with you - this was one of the reasons why I bought a 9210
instead...the 5210 simply couldn't put spaces in the phone numbers.. =/