--nextPart5444580.DvuYhMxLoT Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" On Dienstag, 16. M=E4rz 2021 20:10:46 CET Carl Schwan wrote: > Le mardi, mars 16, 2021 12:55 PM, Harald Sitter a =E9cri= t : > > - since it doesn't appear in the UI, I can't check: is the geodata > >=20 > > actually getting localized? at least the geocoder seems to spit out > > non-localized values >=20 > Yeah, it's not localized :( Cities and region names are using the local > name and countries are using the English name. It probably make sense to > fix the contries name to be localized but the cities/regions names won't > be realistic since there are just too many of them (~137 562). Countries and country subdivisions (regions) are part of the iso-codes=20 translation catalogs we depend on already anyway. See also https:// phabricator.kde.org/T12429 for an API proposal to make that easily accessib= le=20 (needs feedback to continue). Cities also recently came up in the context of KWeather. If we want that, i= t=20 might be doable by compiling the city database ourselves based on OSM/ Wikidata, including all translations found in there. That is very likely al= so=20 not complete, but certainly a lot more realistic than trying to translate t= his=20 ourselves. --nextPart5444580.DvuYhMxLoT Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQQAnu3FVHA48KjZ07R/lszWTRLSRwUCYFOGOAAKCRB/lszWTRLS R3WAAJ99CWinZbI5bw/4B5NbWePPBocgvgCdH2EbfuuLzgU7OfBBtkhmvBaF9oY= =4dfs -----END PGP SIGNATURE----- --nextPart5444580.DvuYhMxLoT--