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
Pelias currently has good support for returning results in multiple languages, using the lang parameter.
However, that parameter only accepts 2 and 3 digit ISO 639 codes.
There are more language variants than these codes can convey. For example, while both Portugal and Brazil speak Portuguese (ISO 639 codes pt and por), many places have names that are different in European and Brazilian Portuguese. For example, the Who's on First record for the region of Bahia, Brazil includes names for both por_x_preferredandpor_br_x_preferred.
Pelias can't currently distinguish these, but we should figure out a way where it can.
In order to support this, we'll need to figure out what a new system for language codes would be (do we just accept anything in WOF? Do we use something more like UNIX locales?), and then make code changes. I'm sure at the very least both the API and Placeholder will need changes, but some importers might as well.
The text was updated successfully, but these errors were encountered:
If regular language/locale codes could be used that would probably be best.
E.g. en_au/en-au for Australian English.
That's a fairly standard way that multilingual applications and websites differenciate between different locales and it's also what browsers send.in Accept-Language headers and is visible in Javascript as navigator.languages.
Pelias currently has good support for returning results in multiple languages, using the
lang
parameter.However, that parameter only accepts 2 and 3 digit ISO 639 codes.
There are more language variants than these codes can convey. For example, while both Portugal and Brazil speak Portuguese (ISO 639 codes
pt
andpor
), many places have names that are different in European and Brazilian Portuguese. For example, the Who's on First record for the region of Bahia, Brazil includes names for bothpor_x_preferred
andpor_br_x_preferred
.Pelias can't currently distinguish these, but we should figure out a way where it can.
In order to support this, we'll need to figure out what a new system for language codes would be (do we just accept anything in WOF? Do we use something more like UNIX locales?), and then make code changes. I'm sure at the very least both the API and Placeholder will need changes, but some importers might as well.
The text was updated successfully, but these errors were encountered: