You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GeocodeOptions only passes along the bare language code to the Geocoding API. For example, even if the system locale is Traditional Chinese (Hong Kong) and the developer sets the locale property to Locale.current, the language query parameter ends up being zh instead of zh-Hant-HK. GeocodeOptions should pass along the entire locale identifier; it would be API’s responsibility to strip any components it doesn’t need or understand.
Sounds good. Subtags will definitely improve results in Chinese in particular, and probably also in a couple of other languages where more than one script is used.
GeocodeOptions only passes along the bare language code to the Geocoding API. For example, even if the system locale is Traditional Chinese (Hong Kong) and the developer sets the
locale
property toLocale.current
, thelanguage
query parameter ends up beingzh
instead ofzh-Hant-HK
. GeocodeOptions should pass along the entire locale identifier; it would be API’s responsibility to strip any components it doesn’t need or understand./cc @apendleton
The text was updated successfully, but these errors were encountered: