chore: update no,nb,nn country-names translation

[Johannes-Andersen]

Update and add missing translations for:

• Norwegian (no)
• Norwegian Bokmål (nb)
• Norwegian Nynorsk (NN)

Also removed nn and nb values where the "no" value was matching. Ref: https://wiki.openstreetmap.org/wiki/Multilingual_names#Norway

Development process:

• Initial batch done by a Node.JS script I wrote to read the yamls, then call the https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DisplayNames API and add nb, no and nn
• Due to amount of mistakes in JS, I did a check against the norwegian lexicon https://snl.no/ for the norwegian name for listed countries.
• Finally I manually went over the changes and validated the names and made minor tweaks and adjustments.

[Johannes-Andersen]

https://www.nrk.no/nyheter/norge-endrer-navnet-pa-hviterussland-til-belarus-1.15983390

[Johannes-Andersen]

Mikronesia is the region, Mikronesiaføderasjonen is the country.

[lonvia]

Thanks for looking into keeping these names up to date.

For the country additions, see the comment in #3837.

Any keys "no" need to be surrounded by double qoutes or yaml will interpret them as "false".

The rules around "nb" are apparently complicated in OSM. Basically it says to use 'name:nb'/'name:nn' only when the spellings differ, otherwise just use name:no. This seems a reasonable rule to follow. The result would rather mean removing a couple of the name:nn though.

[Johannes-Andersen]

For the country additions, see the comment in #3837.

Agree! Removed them now 😁

Any keys "no" need to be surrounded by double qoutes or yaml will interpret them as "false".

Fixed!

The rules around "nb" are apparently complicated in OSM. Basically it says to use 'name:nb'/'name:nn' only when the spellings differ, otherwise just use name:no. This seems a reasonable rule to follow. The result would rather mean removing a couple of the name:nn though.

Hehe, yeah. nn, nb and no are always fun in every i18n project I have seen 😅

I could definitely update the configs to follow that schema! Just a quick question first; how does the fallback logic work?
Example if someone where to just set nn or nb and not no, or if someone has they language set to nb and only nn is set

[lonvia]

There currently is no fallback logic in Nominatim, somewhat under the assumptions that Norwegian speakers are aware that they better provide fallbacks in their language preferences. ;) I would take a PR to add a fallback. Somwhere around here there should be there should be a special case to add 'no' if 'nn' or 'nb' appear without 'no' being in the list.

[Johannes-Andersen]

There currently is no fallback logic in Nominatim, somewhat under the assumptions that Norwegian speakers are aware that they better provide fallbacks in their language preferences. ;) I would take a PR to add a fallback. Somwhere around here there should be there should be a special case to add 'no' if 'nn' or 'nb' appear without 'no' being in the list.

Sounds good!
Went ahead and ran a quick script to do some cleanup 😄

[lonvia]

Looks almost good now, there is just the minor complaint about abbreviations. Also, please squash the commits into one and force push the result.

If Norwegian needs abbreviation forms like "saint" -> "st", then this would need to go into https://github.com/osm-search/Nominatim/blob/master/settings/icu-rules/variants-no.yaml Something for another PR to look at.

[Johannes-Andersen]

If Norwegian needs abbreviation forms like "saint" -> "st", then this would need to go into master/settings/icu-rules/variants-no.yaml Something for another PR to look at.

Nice catch! Removed abbreviations 😄

Also, please squash the commits into one and force push the result.

I think I already did that? 👀 Should just have been one commit I force pushed as I made changes.
Let me know if I need to change anything :D

Thanks for the patience and the feedback!

[lonvia]

Thanks for patiently revising this PR. The CI failure is unrelated and already fixed on an upcoming branch of mine.