* 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
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.
* 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.
* Update CONTRIBUTING.md to introduce Issue Tracker
Also made some template changes for issue filing
* Updating based on lararennie's suggestions
Add back number type
annoucement -> announcement
Google -> Google's
* Update CONTRIBUTING.md
Added the missing requires this detected, removed the extra require. One
missing require was added manually (goog.object) since it's unable to
detect it.
Updated the readme: compiling everything seems to work at the moment.
-- Changing response writer to make it UTF-8. Now carrier/geocoding results have unicode support and don't output "?" characters.
-- Fixing pom file to remove the "repositories" block, now the demo builds on maven. Reordered some other fields to match other pom files. Added some other minor attributes.