Lines Matching refs:regions
76 // by that country calling code. In the case of multiple regions sharing a calling code, such as
77 // the NANPA regions, the one indicated with "isMainCountryForCode" in the metadata should be
81 // The set of regions the library supports.
89 // The set of regions that share country calling code 1.
90 // There are roughly 26 regions and we set the initial capacity of the HashSet to 35 to offer a
330 // Regexp of all known extension prefixes used by different regions followed by 1 or more valid
404 // In some regions (e.g. the USA), it is impossible to distinguish between fixed-line and
490 * Warning: This level might result in lower coverage especially for regions outside of country
521 * Warning: This level might result in lower coverage especially for regions outside of country
566 // The supported regions set does not include the "001" non-geo entity region code.
570 // If the non-geo entity still got added to the set of supported regions it must be because
571 // there are entries that list the non-geo entity alongside normal regions (which is wrong).
572 // If we discover this, remove the non-geo entity from the set of supported regions and log.
782 * typically requires the full national_number to be dialled in most regions).
926 * Convenience method to get a list of what regions the library has metadata for.
943 * commonly used regions.
1046 // Note getRegionCodeForCountryCode() is used because formatting information for regions which
1048 // example, for NANPA regions it will be contained in the metadata for US.
1078 // Note getRegionCodeForCountryCode() is used because formatting information for regions which
1080 // example, for NANPA regions it will be contained in the metadata for US.
1140 // Note getRegionCodeForCountryCode() is used because formatting information for regions which
1142 // example, for NANPA regions it will be contained in the metadata for US.
1263 * is used. For regions which have multiple international prefixes, the number in its
1286 // For NANPA regions, return the national format for these regions but prefix it with the
1291 // If regions share a country calling code, the country calling code need not be dialled.
1303 // For regions that have multiple international prefixes, the international format of the
1499 * input _and_ is the start of the national number. This is not a problem in the regions
1643 // Note in some regions, the national number can be written in two completely different ways
1994 // For regions where we don't have metadata for PhoneNumberDesc, we treat any number passed in
2014 List<String> regions = countryCallingCodeToRegionCodeMap.get(countryCode);
2015 if (regions == null) {
2021 if (regions.size() == 1) {
2022 return regions.get(0);
2024 return getRegionCodeForNumberFromRegionList(number, regions);
2049 * region code being found, ZZ will be returned. In the case of multiple regions, the one
2108 * <p>Warning: Do not use this method for do-your-own formatting - for some regions, the
2141 * @return true if regionCode is one of the regions under NANPA
2219 * <li> For fixed line numbers, many regions have the concept of area code, which together with
2237 // various regions within those plans.
