@ Azzie

Belarus is unsupported , at address 0x593D you have 10 00 00 00 00 00
you must add an Header with 80 as Trunk prefix and 810 as international
+375 is added automatically

for area codes with 2 digits (29),(17) you must create a sub-block type 2
and a rule for every code , but if you have 29,30,31 you can use one rule
for a range (XX >= 29 and XX <= 31)
another sub-block type 3 for (177) an so on ...

string1 try: n (##) #######
string2 try: n (###) #######

but I am not sure

So difficult for me

Someone could change the US format for:
<string>(01#) ####-####</string>
<string>(02#) ####-####</string>
<string>(03#) ####-####</string>
<string>(04#) ####-####</string>
<string>(05#) ####-####</string>
<string>(06#) ####-####</string>
<string>(07#) ####-####</string>
<string>(08#) ####-####</string>
<string>(09#) ####-####</string>
<string>0#00 ### ####</string>
<string>0#00 ## ####</string>
<string>(0##-##) ####-####</string>
<string>+55 ## ####-####</string>
<string>####-####</string>
<string>####</string>
<string>## ###<string>
<string>(00##) $</string>
And send me the file? Pleaseee...

I`m from Brazil, I wanna use my iPhone in English but with the brazilian region format. If I change it in Region Format menu, the date format change too, and I wanna all my iPhone in english.

Thank you.
Bye

too complex, to view the numbers with spaces

So difficult for me to

Someone could change the US format for:

<string>+381(##) ###-####</string>
<string>(0##) ###-####</string>
<string>(0##) ####</string>
<string>###-####</string>
<string>####</string>

Thanx , Please...

I've written a quick outline of how the format works. You can get it at http://mail.sparecreative.com//UIPho...ormat_Mods.pdf I don't have a lot of band width, so if somebody would like to host a copy elsewhere I'd appreciate it.

Originally Posted by Frank8

May be my first 2.1 complete fix : Australia
can someone test it ?

old style plist equivalent:

04## ### ###
+61 4## ### ###
#### ####
(02) #### ####
(03) #### ####
(07) #### ####
(08) #### ####
+61 2 #### ####
+61 3 #### ####
+61 7 #### ####
+61 8 #### ####
1300 ### ###
1800 ### ###
1900 ### ###
13 ## ##

using 0xED editor:

address 0x1FC
36 31 00 00 61 75 00 00 EE 49 00 00----------61 au --
modify to:
36 31 00 00 61 75 00 00 C0 56 00 00----------61 au --

add this data at the end of file address 0x6136
------------------------00 00 14 00 00 00 CC 00 00 00
04 00 00 00 30 00 30 30 31 31 00 00 04 00 03 00
14 05 00 00 14 05 00 00 0A 00 00 00 28 00 00 00
08 07 00 00 08 07 00 00 0A 00 00 00 28 00 00 00
6C 07 00 00 6C 07 00 00 0A 00 00 00 28 00 00 00
02 00 01 00 0D 00 00 00 0D 00 00 00 06 00 00 00
3F 00 00 00 01 00 08 00 01 00 00 00 09 00 00 00
08 00 00 00 35 00 00 00 01 00 00 00 03 00 00 00
09 00 00 00 00 00 00 00 04 00 00 00 04 00 00 00
09 00 00 01 1B 00 00 00 05 00 00 00 09 00 00 00
09 00 00 00 00 00 00 00 02 00 00 00 02 00 00 00
09 00 00 01 0C 00 00 00 03 00 00 00 03 00 00 00
09 00 00 01 0C 00 00 00 07 00 00 00 07 00 00 00
09 00 00 01 0C 00 00 00 08 00 00 00 08 00 00 00
09 00 00 01 0C 00 00 00 23 20 23 23 23 23 20 23
23 23 23 00 28 6E 23 29 20 23 23 23 23 20 23 23
23 23 00 6E 23 23 23 20 23 23 23 20 23 23 23 00
23 23 23 23 20 23 23 23 20 23 23 23 00 23 23 23
23 20 23 23 23 23 00 23 23 20 23 23 20 23 23 00

remember to respring or restart when file is substituted.

YAY!

Thanks Frank8, it works for me perfectly now!

One thing though; I had to add another "00" before i pasted the big chunk of code to make it line up at 6136 (otherwise it would have been at 6135). I'm not sure whether it would or wouldn't have worked otherwise, but they way i did it seems great.



Yay!

The mistery of byte_11 :

Rules are made with 16 bytes , byte_01 to byte_16

01 00 00 00 09 00 00 00 09 00 00 00 00 00 00 00

and sometimes byte_12 is 01

04 00 00 00 04 00 00 00 09 00 00 01 00 00 00 00

for me it tell that the rule condition is applied to
the second digit if first is "0"

for some countries byte_11 is not zero

01 00 00 00 09 00 00 00 09 00 03 00 00 00 00 00

and generally the value is equal to the length
of the area code in the designated string

example byte_11 = 03 and string1 = ### ######

apparently not necessary , is used to solve special cases ?

Do we know the algorithm by which UIKit will eventually make a choice between ways to display numbers? The first step is clear: it decides what country to use for the number and looks up the specs for that country in UIDefaultFormats.phoneformat. But there it finds a list of formats. How does it choose from them?

For example, in UIDefaultFormats.phoneformat at offset 0x2408 there are these formats (I don't know which country, but that doesn't matter):

1. ## ########## (2+10=12 digits)
2. ### ####### (3+7=10 digits)
3. ## ######### (2+9=11 digits)
4. ## ######## (2+8=10 digits)
5. ### ########
6. ### ######
7. # ##########

Suppose the number has 10 digits, say it's 1234567890. How does UIKit decide whether to use display option 2 (123 4567890) or 4 (12 34567890)?

Jim,

it's for Finland (+358) , real offset 0x228C

you can read the document made from "spare" at #99

Hi Frank,

I'm almost ready with the Belgium hex version but ran into something.
On line 3 "04 00 00 00 - 4 sets of rules (4 bytes)" you specify 4 set of rules and only
see 3 coded. Can I change it to "03 00 00 00"?

Thanks :-)

Jo.