phonelib 0.6.5 → 0.6.6

data/data/libphonenumber/AUTHORS

@@ -1,4 +0,0 @@
-Google Inc.
-Vonage Holdings Corp.
-Ian Galpin
-Ben Gertzfield

data/data/libphonenumber/CONTRIBUTING.md

@@ -1,47 +0,0 @@
-# Contributing to libphonenumber
-
-Thanks for contributing to libphonenumber!
-
-Please read the following before filing an issue. **Note that we are _not_ accepting pull requests for metadata updates at this time.**
-
-## Checklist before filing an issue
-
-Please check the following:
-* Has the issue already been discussed in the [open issues](https://github.com/googlei18n/libphonenumber/issues) or [discussion group](https://groups.google.com/group/libphonenumber-discuss)? If so, you may want to comment on an existing discussion.
-* Is the issue reproducible using the [demo](http://libphonenumber.appspot.com/)? If not:
-    + Your issue may be resolved by upgrading to the latest version of the library.
-    + If you are using a [port](https://github.com/googlei18n/libphonenumber#known-ports), issues should be reported against that project.
-    + If you are using the library through a front-end or wrapper, issues should be reported against that project.
-
-
-## Filing a metadata issue
-
-Please copy this template into your report and answer the questions to the best of your ability.
-* Country/region affected (e.g., "US"):
-* Example number(s) affected ("+1 555 555-1234"):
-* The phone number range(s) to which the issue applies ("+1 555 555-XXXX"):
-* The type of the number(s) ("fixed-line", "mobile", "short code", etc.):
-* The cost, if applicable ("toll-free", "premium rate", "shared cost"):
-* Supporting evidence (for example, national numbering plan, announcement from mobile carrier, news article): [see below](#provide-supporting-evidence)
-
-
-### Provide supporting evidence
-
-Ideally, change requests for ranges should be accompanied by authoritative evidence such as official government or public carrier documents.
-
-If the evidence is publicly available online, please provide the link.
-
-If the evidence is not publicly available online, make sure that you have the rights to share this with us, and confirm this by reading and signing the appropriate Contributor License Agreement (CLA):
-* If you are contributing as an individual, sign the [individual CLA](https://cla.developers.google.com/about/google-individual?csw=1).
-* If you are contributing as part of a corporation, sign the [corporate CLA](https://developers.google.com/open-source/cla/corporate?csw=1).
-
-**By signing the CLA, you confirm that you have the rights to share the information with us, and that we may use, modify, reproduce, publicly display, and distribute the information in accordance with the library's [open source license](https://github.com/googlei18n/libphonenumber/blob/master/LICENSE).**
-
-Once you have signed the CLA, you can [request to be whitelisted]
-(https://groups.google.com/forum/#!managemembers/libphonenumber-supporting-docs) to send emails to the [libphonenumber-supporting-docs](mailto:libphonenumber-supporting-docs@googlegroups.com) mailbox. Put the GitHub issue number in the subject line and attach the supporting documents. Only the core libphonenumber team has access to view emails sent to this mailbox.
-
-## Filing a code issue
-
-When filing a code issue, include the specifics of your operating system and provide as much information as possible that helps us reproduce the problem.
-
-Please be advised that metadata updates are prioritized over code changes, except for bug fixes. In addition, we work with a limited number of build systems and may not be able to support every setup.

data/data/libphonenumber/CONTRIBUTORS

@@ -1,69 +0,0 @@
-# This is the list of people who have contributed to the repository.
-# The AUTHORS file lists the copyright holders; this file
-# lists people.  For example, Google employees are listed here
-# but not in AUTHORS, because Google holds the copyright.
-
-# Core team:
-# 
-# These people were responsible for the initial implementations in Java and
-# C++, and carry out the bulk of metadata maintenance, bug fixes & feature
-# requests, and porting new features to Javascript.
-
-Shaopeng Jia
-Lara Rennie
-David Yonge-Mallo
-David Beaumont
-
-# Additional contributions:
-
-# Javascript
-Nikolaos Tronikos
-    -- Initial implementation, some subsequent maintenance.
-
-# Java:
-Walter Erquínigo
-    -- Timezone mapper.
-Philippe Liard
-    -- Offline geocoder, local Maven expert.
-Cecilia Roes
-    -- Carrier mapper.
-Tom Hofmann
-    -- First version of the PhoneNumberMatcher and related classes.
-Fabien Allanic
-Kushal Pisavadia
-
-# C++:
-Patrick Mézard
-    -- Geocoding library implementation.
-Philippe Liard
-    -- Initial open-sourcing of a C++ library, responsible for getting this to
-       work across multiple platforms.
-Ben Gertzfield
-Fredrik Roubert
-George Yakovlev
-Nico Weber
-Yoshifumi Inoue
-
-# Debian:
-Fredrik Roubert
-
-# Metadata:
-Alec McTurk
-Alexandru Manea
-András Eisenberger
-Anssi Hannula
-Boshi Lian -- Maintains Chinese geocoding data
-Bradford Smith
-Cecilia Roes
-Florian Görisch
-Fredrik Roubert
-Ian Galpin -- Maintains the data for the UK
-Javier Kohen
-Jeanine Lilleng
-Karen Lees
-Khaled Hafez
-Lei Zhang
-monjiwired@
-Philippe Liard
-Sang-il Lee
-Yugui Sonoda

data/data/libphonenumber/FALSEHOODS.md

@@ -1,237 +0,0 @@
-# Falsehoods Programmers Believe About Phone Numbers
-
-... and tips on how to use libphonenumber.
-
-Given how ubiquitous phone numbers are and how long they've been around, it's
-surprising how many false assumptions programmers continue to make about them.
-
-1.  **An individual has a phone number**
-
-    Some people do not own phones, or do not wish to provide you with their
-    telephone number when asked. Do not require a user to provide a phone number
-    unless it is essential, and whenever possible try and provide a fallback
-    to accommodate these users.
-
-1.  **An individual has only one phone number**
-
-    Obviously, this isn't necessarily true.
-
-1.  **A phone number uniquely identifies an individual**
-
-    It wasn't even that long ago that mobile phones didn't exist, and it was
-    common for an entire household to share one fixed-line telephone number. In
-    some parts of the world, this is still true, and relatives (or even friends)
-    share a single phone number. Many phone services (especially for businesses)
-    allow multiple inbound calls to or outbound calls from the same phone
-    number.
-
-1.  **Phone numbers cannot be re-used**
-
-    Old phone numbers are recycled and get reassigned to other people.
-
-1.  **Phone numbers that are valid today will always be valid. Phone numbers of
-    a certain type today (e.g., mobile) will never be reassigned to another
-    type.**
-
-    A phone number which connects today may be disconnected tomorrow. A number
-    which is free to call today may cost money to call tomorrow. The phone
-    company may decide to expand the range of available phone numbers by
-    inserting a digit into an existing number.
-
-    **Tip:** Don’t store properties for a phone number such as validity or
-    type. Check this information again from the library when you need it.
-
-1.  **Each country calling code corresponds to exactly one country**
-
-    The USA, Canada, and several Caribbean islands share the country calling
-    code +1. Russia and Kazakhstan share +7. These are not the only examples!
-
-1.  **Each country has only one country calling code**
-
-    As of this present moment (in Mar. 2016), phones in the disputed territory
-    and partially recognised state of Kosovo may be reached by dialing the
-    country calling code for Serbia (+381), Slovenia (+386), or Monaco (+377),
-    depending on where and when one obtained the number.
-
-    **Tip:** Use a phone widget to encourage users to enter their phone number
-    in an international format such that it can be unambiguously understood.
-
-1.  **A phone number is dialable from anywhere**
-
-    Some numbers can only be dialed within the country. Some can only be dialled
-    from within a subset of countries, such as the international 00800 numbers.
-    Some may be dialable only if the caller is a subscriber to a particular
-    telecom company.
-
-1.  **You can send a text message to any phone number**
-
-    A lot of people still only have a fixed-line telephone, which typically cannot
-    send or receive text messages.
-
-    **Tip:** Whenever possible, try and accommodate these users by calling them
-    with a voice message or voice prompts. Alternatively, if your service
-    requires sending text messages, verify that the number can receive text
-    messages after the user provides it.
-
-1.  **Only mobile phones can receive text messages**
-
-    Some service providers support sending and receiving text messages to fixed-line
-    numbers. There are also online services like Skype that can send and receive
-    text messages.
-
-1.  **There are only two ways to dial a phone number: domestically and from
-    overseas**
-
-    Some numbers may need different prefixes depending on: the carrier you are
-    using; what device you are dialling from/to; whether you are inside or
-    outside a particular geographical region.
-
-    Examples:
-    *   In Brazil, to dial numbers internally but across a certain geographical
-        boundary, a carrier code must be explicitly dialed to say which carrier
-        you will use to pay for the call.
-    *   In Nepal, the leading zero in national format is omitted depending on
-        whether the originating phone is mobile or fixed-line.
-    *   In New Zealand, you need to dial the area-code (e.g. 03) even if the
-        number is within the same area-code region as you are, unless it is
-        "close" (something approximating city/district boundaries), in which
-        case it shouldn’t be dialled.
-
-    **Tip:** Use formatForMobileDialling to get the number a user should
-    actually dial on their mobile phone.
-
-1.  **To make a number dialable, you only need to change the prefix**
-
-    In Argentina, to dial a mobile number domestically, the digits "15" need to
-    be inserted *after* the area code but *before* the local number, and the "9"
-    after the country code (54) needs to be removed. This transforms +54 9 2982
-    123456 into 02982 15 123456.
-
-1.  **No prefix of a valid phone number can be a valid phone number**
-
-    In some countries, it's possible to connect to a different endpoint by
-    dialing more digits after a number. So "12345678" may not reach the same
-    person as dialing "123456".
-
-1.  **An invalid number will not reach an endpoint**
-
-    In some countries, or on some phones, extra digits are thrown away. Hence,
-    1-800-MICROSOFT is an invalid number - but it still connects to Microsoft,
-    since any later digits are ignored. Numbers such as "911" can be reached by
-    dialling "911 123" in some countries: but not in others.
-
-    In other countries, invalid numbers may be "fixed" by a carrier, e.g.,
-    adding a mobile token if they know it is a mobile number, such that it
-    connects.
-
-1.  **All valid phone numbers follow the ITU specifications**
-
-    ITU-T specifies that a phone number cannot be longer than fifteen digits,
-    with one to three digits reserved for the country calling code, but valid
-    numbers in Germany have been assigned that are longer than this.
-
-1.  **All valid phone numbers belong to a country**
-
-    There are many "country calling codes" issued to non-geographical entities,
-    such as "800" or satellite services.
-
-1.  **Phone numbers contain only digits**
-
-    In Israel, certain advertising numbers start with a `*`. In New Zealand,
-    non-urgent traffic incidents can be reported by calling `*555` from a mobile
-    phone.
-
-1.  **Phone numbers are always written in ASCII**
-
-    In Egypt, it is common for phone numbers to be written in native digits.
-
-1.  **Phone numbers have only one prefix (area code or national destination
-    code) at a given time**
-
-    In the mid-90s in Iceland, phone numbers changed from 5 and 6 digits to 7
-    digits. The old system had regional prefixes, but the new one doesn't.
-    During the transition period, phone numbers could be reached by the old area
-    code or the new 7 digit number (a different prefix).  For example, a
-    Reykjavik phone number could be dialed with `nnnnn` and `55nnnnn` inside the
-    region, and `91-nnnnn` and `55nnnnn` from outside.
-
-    **Tip:** During transition periods, make sure that both forms of a number
-    are supported for look-up by phone number. If sending messages/dialling
-    affected numbers, both the new and old prefix may need to be tried.
-    Depending on the type of transition, you may need to contact affected
-    customers and ask them to update their number.
-
-1.  **A leading zero in numbers formatted for domestic usage can always be
-    discarded when dialing from abroad**
-
-    In some countries, people write the national prefix in brackets (typically
-    `(0)`) after the country calling code to indicate that it should be
-    discarded when dialing internationally. In Italy, since 1988, the prefix was
-    "fixed" to the phone numbers, so that `(01) 2345` became `012345` and should
-    be dialed (internationally) as `+39012345` (including the leading zero).
-
-    **Tip:** Use the library to parse and format numbers to handle this
-    correctly for every country.
-
-1.  **The country or area code of a phone number indicates the user's location,
-    place of residence, time-zone, or preferred language**
-
-    There are many reasons for someone to have a phone number issued in a state
-    or region other than where they reside or hold citizenship.
-
-    These include, but are not limited to:
-    *   *Moving within a country*: In countries with phone number portability,
-        you may retain your number when moving, even in some cases if it is a
-        fixed-line number and even if it has an area code. (See
-        [xkcd](https://xkcd.com/1129/) for a US example.)
-    *   *Moving to another country*: Some people keep their mobile phones when
-        they move to another country.
-    *   *Geopolitical turmoil*: Sometimes countries change their borders, cease
-        to exist, or come into existence.
-    *   *Business, family, and friends*: A business may have many customers in a
-        neighbouring country, or a person may have many family and friends
-        there.
-    *   *Wanting cheaper rates*: VoIP is often cheaper than regular calls.
-        People traveling around Europe may get a SIM card from one country and
-        have a roaming plan.
-
-    Note that geographical area codes are assigned in some countries to mobile phones.
-
-    **Tip:** Programmers should not disallow users from signing up with a phone
-    number merely because it belongs to another country. Care should be taken
-    when calling methods such as `isValidNumberForRegion` that this is what's
-    actually intended. If you have a phone input widget, make sure you allow
-    numbers to be entered in international format (i.e., allow the `+` sign) so
-    people can sign up with an international contact number.
-
-1.  **The plus sign in front of phone numbers in international format is
-    optional, or can always be replaced by `00`**
-
-    The plus sign is part of the [E.164
-    format](https://en.wikipedia.org/wiki/E.164) for international telephone
-    numbers. It can be replaced with the [international call
-    prefix](https://en.wikipedia.org/wiki/List_of_international_call_prefixes)
-    when dialing internationally. Note that while `00` is a common international
-    call prefix, this actually varies by country.
-
-    In North America, which has a country calling code of `+1`, it is a common
-    error to drop the `+` in front of the number and write it like
-    `1-555-123-4567`. This is technically incorrect. To call this number from
-    Japan, where the international call prefix is `010`, one may dial either `+1
-    555 123 4567` or `010 1 555 123 4567`.
-
-1.  **Users will only store phone numbers in your product's phone number fields**
-
-    Some users use their contact lists to store things like birthdays or other
-    information. Unless a piece of user-supplied data has actually been verified
-    to be a phone number, it should be stored as-is as entered by the user.
-
-1.  **Phone numbering plans published by governments or telecoms represent
-    reality**
-
-    National numbering plans, such as those administered by the
-    [ITU](http://www.itu.int/oth/T0202.aspx?parent=T0202), represent the
-    intentions of the government or telecom. These may be published before,
-    during, or after the actual implementation of numbering plan changes in the
-    real world. The actual date on which a phone number range becomes active may
-    not always adhere to official announcements.

data/data/libphonenumber/FAQ.md

@@ -1,190 +0,0 @@
-# Frequently Asked Questions (FAQ)
-
-## Validation and types of numbers
-
-### What is the difference between isPossibleNumber and isValidNumber?
-
-To understand the behavior of functions, please refer to the documentation in
-the Javadoc/C++ header files. For example, see `isPossibleNumberWithReason` in
-[`PhoneNumberUtil`]
-(https://github.com/googlei18n/libphonenumber/blob/master/java/libphonenumber/src/com/google/i18n/phonenumbers/PhoneNumberUtil.java).
-
-### Why does PhoneNumberUtil return false for valid short numbers?
-
-Short numbers are out of scope of
-[`PhoneNumberUtil`]
-(https://github.com/googlei18n/libphonenumber/blob/master/java/libphonenumber/src/com/google/i18n/phonenumbers/PhoneNumberUtil.java).
-For short numbers, use
-[`ShortNumberInfo`]
-(https://github.com/googlei18n/libphonenumber/blob/master/java/libphonenumber/src/com/google/i18n/phonenumbers/ShortNumberInfo.java).
-
-### What does it mean for a phone number to be valid?
-
-Our phone number library can tell that a number range is valid when there is
-sufficient official documentation, with some latency after this fact is brought
-to our attention via issue reports or notifications (see below for more
-information on where our metadata comes from). A valid number range is one from
-which numbers can be freely assigned by carriers to users.
-
-Do not rely on libphonenumber to determine whether numbers are currently
-assigned to a specific user and reachable. Some products (e.g.
-[Google 2-step verification] (https://www.google.com/landing/2step/)) do
-this with a verification step e.g. by sending an SMS or placing an automated
-phone call with a verification code). This is not technically feasible without
-such a verification step given the complicated international world we live in,
-with varying standardization practices in different regions.
-
-#### But my dialled number connected, so isn't it valid?
-
-Not necessarily. In some countries extra digits at the end are ignored. For
-example, dialling `1800 MICROSOFT` in the US connects to `+1 (800) MIC-ROSO`.
-Moreover, during renumbering transitions, e.g. when all numbers are getting an
-extra `9` added to the front, some carriers will "fix" old numbers long after
-they're no longer working for the majority.
-
-### When should I use isValidNumberForRegion?
-
-Rarely! Many people have phone numbers that do not belong to the country they
-live in. This applies particularly to mobile numbers, but may also be true
-for VoIP numbers etc. Note also that the regions your application supports may
-not be the same as the regions we support. For example, the Channel Islands such
-as "Jersey" have their own region code - JE. If you allow these users to sign up
-as a British user ("GB"), their phone numbers will not be considered valid for
-the region "JE".
-
-One use-case where this method may be useful is if you want to see if a
-`FIXED_LINE` number for a business matches the country it is in, to try and spot
-data errors.
-
-### What types of phone numbers can SMSs be sent to?
-
-SMSs can be sent to `TYPE_MOBILE` or `TYPE_FIXED_LINE_OR_MOBILE` numbers. However,
-in some countries it is possible to configure other types, such as normal
-land-lines, to receive SMSs.
-
-### Why did I get `TYPE_FIXED_LINE_OR_MOBILE` as the type of my phone number?
-
-Some number ranges are explicitly defined as being for fixed-line or mobile
-phones. We even represent ranges defined as being "Mostly land-line" in this
-way.
-
-### What is mobile number portability?
-
-The ability to keep your mobile phone number when changing carriers. To see whether a region supports mobile number portability use [isMobileNumberPortableRegion](https://github.com/googlei18n/libphonenumber/blob/master/java/libphonenumber/src/com/google/i18n/phonenumbers/PhoneNumberUtil.java#L3275).
-
-### Since it's possible to change the carrier for a phone number, how is the data kept up-to-date?
-
-Not all regions support mobile number portability. For those that don't, we return the carrier when available. For those that do, we return the original carrier for the supplied number.
-
-### What about M2M (machine to machine) numbers?
-
-libphonenumber does not support M2M numbers at the moment, but might in the
-future.
-
-One of the reasons libphonenumber doesn't support M2M so far is because no one
-could explain their use to us sufficiently.
-
-We don't require that a number to be supported by the library has a human at the
-other end since we already accept premium rate services and they might go to an
-automated system instead. But to date we only accept ranges that a human might
-call or send an SMS to.
-
-M2M numbers would violate this assumption and we'd have to evaluate the
-consequences for existing APIs and clients if M2M numbers would be considered
-valid by the library.
-
-Many people use this library for formatting the numbers of their contacts, for
-allowing people to sign up for services, for working out how to dial someone in
-a different country, for working out what kind of cost might be associated with
-a number in an advert, etc. We don't think the lack of M2M support hinders any
-of those use-case, but we might be wrong.
-
-If you would like libphonenumber to support M2M numbers, please engage with the
-developer community at [Support M2M numbers #680]
-(https://github.com/googlei18n/libphonenumber/issues/680) with further
-information to address our questions and concerns and please describe what kinds
-of use-cases fail because M2M numbers are not supported by the library.
-
-More information on this issue would be very welcomed!
-
-Related issues: [Support M2M numbers #680]
-(https://github.com/googlei18n/libphonenumber/issues/680),
-[#930: JTGlobal - an MNO based in the UK]
-(https://github.com/googlei18n/libphonenumber/issues/930), [#976: Norway]
-(https://github.com/googlei18n/libphonenumber/issues/976), [#985: South Africa,
-Vodacom](https://github.com/googlei18n/libphonenumber/issues/985), [#910:
-Sweden](https://github.com/googlei18n/libphonenumber/issues/910), [#657:
-Canada](https://github.com/googlei18n/libphonenumber/issues/657), [#550:
-Belgium](https://github.com/googlei18n/libphonenumber/issues/550), [#351:
-Norway](https://github.com/googlei18n/libphonenumber/issues/351), [#332:
-Netherlands](https://github.com/googlei18n/libphonenumber/issues/332)
-
-## Representation
-
-### What is the maximum and minimum length of a phone number?
-
-We support parsing and storing numbers from a minimum length of two digits to a
-maximum length of 17 digits currently (excluding country calling code). The ITU
-standard says the national significant number should not be longer than
-fifteen digits, but empirically this has been proven not to be followed by all
-countries.
-
-## Formatting
-
-### Can / should we format phone numbers in a language-specific way?
-
-No, phone number formatting is country-specific and language-independent. E.g.
-formatting a US number in a French way (e.g. the way a France number is
-formatted) for a French user is undefined and wrong.
-
-It is true that in some countries phone numbers are typically written using
-native, not ASCII, digits; our phone number library supports parsing these but
-doesn't support it at formatting time at the moment.
-
-### Why does formatNumberForMobileDialing return an empty string for my number?
-
-If we don't think we can guarantee that the number is diallable from the user's
-mobile phone, we won't return anything. This means that for numbers that we
-don't think are internationally diallable, if the user is outside the country
-we will return an empty string. Similarly, in Brazil a carrier code is essential
-for dialling long-distance domestically. If none has been provided at parsing
-time then we will return an empty string. If you get an empty string and are
-okay providing a number that may not be diallable, you can call another of our
-formatting numbers instead.
-
-## Metadata
-
-### <a name="metadata_definition"></a>What do we mean by "metadata"?
-
-We use the word "metadata" to refer to all information about phone numbering in
-a particular country - what the country code, international and national
-dialling prefixes are, what carrier codes are operational, which phone numbers
-are possible or valid for a particular country, how to optimally format them,
-which prefixes represent a particular geographical area, etc.
-
-### Where do we get information from to determine if a number range is valid?
-
-In theory, phone numbering plans are all supposed to be administered through the
-ITU. Many countries' phone numbering plans may be found on the [ITU website](
-http://www.itu.int/oth/T0202.aspx?parent=T0202).
-
-We receive automatic notifications when a new ITU plan has been filed, which may
-or may not be before it comes into effect.
-
-Not every country files their numbering plans with the ITU nor are the plans
-filed with ITU always up to date. In some countries, the numbering plans are
-directly handled by a government authority, while in others, most of the work
-is done by telecom companies (the government's role being only to distribute
-ranges at the prefix level, with the actual partitioning within the prefix done
-by the telecom).
-
-A large part of the data in `PhoneNumberMetadata.xml` comes from the ITU
-documents, but because they're sometimes insufficient, we also include data from
-other sources, including user bug reports, telecom company home pages and
-government telecommunication authorities.
-
-There is no RFC indicating where the data comes from, or what format they're in.
-
-We'd love to consume machine-readable numbering plan data (assigned ranges,
-carrier & geo mappings). If you can connect us with partners in the industry
-to achieve this, please do so. Thanks!