*   It was confusing and unnecessary. Not every country that has short numbers beginning with a 0 had it, and it is not the only digit that could overlap with a national prefix and hence be interpreted incorrectly.

* [maven-release-plugin] prepare release v8.5.2

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.5.1

* [maven-release-plugin] prepare for next development iteration

* Metadata updates for release 8.5.1

* Update release_notes.txt

Update the demo version in README file as part of release 8.5.0.

* [maven-release-plugin] prepare release v8.5.0

* [maven-release-plugin] prepare for next development iteration

* Metadata updates for release 8.5.0

* Corrected release notes as US geocding update is mentioned as new addition.

* Make canBeInternationallyDialled_API public in Java and CPP
* update notes in pending_code_changes.txt
* Remove TODO on canBeInternationallyDialled as it is already an public API in JS
* Make JS canBeInternationallyDialled API doc consistent with Java and CPP

* [maven-release-plugin] prepare release v8.4.3

* [maven-release-plugin] prepare for next development iteration

Alternate metadata and test metadata for C++ was regenerated not due to changes in this commit, but due to PR #1726 and that they should have been updated then.

* Updating the phonemetadata.pb.js file, deleting handling for a field
that does not exist, and adding a couple of @final notes for the closure
compiler.

Relevant docs: https://docs.travis-ci.com/user/installing-dependencies/
Change was made by Travis on May 4th.

Commit log:
eac577dbf8
Relevant diff:
-ant-optional

* Add FAQ for number removals

Someone reported this recently and filing through Issue Tracker will anonymize the report.

* clarify example number usage

* Add FAQ about range overlaps

Specific examples about AR and MX provide since they are countries with varied lengths, formats and prefixes depending on context.

* Range overlaps updates 

Integrated feedback from @lararennie

* FIXED_LINE_OR_MOBILE reference

* last cleanup

1) Changing the BuildMetadataFromXml to only set
same_mobile_and_fixed_line_pattern and
national_prefix_optional_when_formatting if they differ from default
values, and the domestic_carrier_code_formatting_rule,
international_prefix and national_prefix_formatting_rule if there is
one.

2) Adding a test with some golden data for the BuildMetadataJsonFromXml.

3) Adding to the proto a missing explicit default false.

4) Updating a couple of methods in the Phonemetadata.java class to have
names that match those of the auto-generated Phonemetadata used by the
CPP build, now that we use those methods when building the metadata.

5) Fix to ant build file to enable the junit command to still work (instructions on open-source on how to regenerate metadata files refer to this)

Resulting data is smaller for Java and C++ and the resulting BuildMetadataJsonFromXml code is cleaner.

* Update M2M FAQ with more specific requests

Add more context how it's not just more metadata sources/countries we need, but also how to technically support M2M.

* Add example of M2M challenges

* Update FAQ.md

* remove mystery whitespace

* Handling possible out-of-bounds exception that would be thrown in C++
and Java if a number with a phone-context tag is entered (RFC3966
format) but no actual phone context.