Aug 24, 2016: libphonenumber-7.6.0
Code changes:
Refactored metadata loading and closed all streams after loading.
Made isNumberGeographical public, and changed the geocoder to use this when checking whether to give a detailed answer or country-level only.
Build changes:
Use protobuf-javanano 3.0.0-alpha-7 from Maven Central.
Metadata changes:
Updated phone metadata for region code(s): EH, ET, JM, MA, SK, SN, SY, ZM
Updated short number metadata for region code(s): ZA
Updated geocoding data for country calling code(s): 212 (en)
New carrier data for country calling code(s): 86 (zh, zh_Hant), 852 (zh, zh_Hant), 963 (en)
Updated carrier data for country calling code(s): 86 (en), 212 (en), 251 (en), 421 (en)
Deleted unsupported SingleFilePhoneNumberMetadataProto
Making function IsNumberGeographical public. This function operates on
the type of number and the country it belongs to only, so may have some
false positives.
Using this in the geocoder so that geocoding now limited to numbers that
we consider geographical, based on their type and country, rather than
just based on their type. The C++ geocoder did not previously check the
number type/country at all.
Indonesian and Chinese mobile numbers have now been added to the list of
possibly-geographical numbers.
Hello,
I noticed that the number +212682 was not detected as correct by the library i checked the national numbering plan for the governing authority and i saw it was valid number ,
After checking the code i saw many mistakes, I made changes according to the file from ANRT that is published on the website under :
https://www.anrt.ma/sites/default/files/blocs_de_numeros_par_operateur_juillet_2016.pdf
Best regards,
Alaa TOUNSADI
I translated English Version of Afghanistan geocoding to Persian.
Note: One of two official languages in Afghanistan is Persian Dari Persian/ Dari Farsi.