Opened 9 years ago

Closed 8 years ago

#2800 closed enhancement (fixed)

Change language code for Norwegian (Bokmål) from "no" to "nb"

Reported by: Hans Nordhaug Owned by: s.mazeland@…
Priority: minor Milestone:
Component: website Version:
Keywords: Cc:


Currently the OSM website (and Potlatch) is using "no" as language code for Norwegian. What is called Norwegian is in fact Norwegian Bokmål. (The other written language in Norway is Nynorsk (nn) which currently isn't used or even supported by OSM.) The language code "no" is deprecated. Please replace "no" with "nb" (and "Norsk" with "Norsk Bokmål").

Change History (7)

comment:1 Changed 9 years ago by Tom Hughes

Resolution: invalid
Status: newclosed

We're using whatever codes people submit translations for on Translatewiki. If you want to submit translations for nb then you can do so here:

If you want to argue that Translatewiki is using the wrong code and should change and move the existing translations then you will need to talk to Translatewiki people about it.

comment:2 Changed 9 years ago by s.mazeland@…

Resolution: invalid
Status: closedreopened
Type: defectenhancement

I asked Hans to register it here, because in the end it impacts the L10n structure of OpenStreetMap, independent from the way the translation is organised. If any discussion would arise regarding no/nb in OpenStreetMap, this would be the place to discuss it, and the consequences would have to be visible in translatewiki. I wouldn't want to force the non-translator users of OSM to have to go to a different environment.

I expect to be able to get the request from this ticket closed within the next few days. If possible, please assign the issue to me.

comment:3 Changed 9 years ago by s.mazeland@…

Owner: changed from Tom Hughes to s.mazeland@…
Status: reopenednew

comment:4 Changed 9 years ago by Tom Hughes

I'm happy to leave it open, although I don't think it will impact our structure significantly - anything committed becomes available on the site without having to do anything to configure a new language.

Our language list (used for choosing the language of diary entries etc) already has both nb and no in it.

The only issue might be one of wanting to alias the two together somehow.

There is also an issue that the rails translations are currently using no-NB and no-NN so we may need to do some clever magic to merge them in. I suspect that issue already arises with other languages anyway.

comment:5 Changed 9 years ago by s.mazeland@…

Status: newassigned

From IRC. Haven't had a reply from Tom yet. Want to wait for his input before doing anything. IMO this will provide fixes for all the language mapping issues without requiring any tricks in OSM or rails i18n. Of course, any issues in rails i18n have to be reported on/fixed in rails-i18n.

siebrand TomH: had a brief discussion with avar about issue #2800 siebrand TomH: wanted to discuss my plans with you before making actual changes. siebrand TomH: the idea is this. Revert [20551] and [20550], make a mapping at for a few languages, so that the exported files mat whatever is in . That should work.

comment:6 Changed 9 years ago by Tom Hughes

I'd rather not revert 20550 really - as far as I can see no-NB and no-NN are clearly nonsensical as NB and NN are not valid country codes. I've actually attempted to upstream that change although I've no idea if they'll take it or not.

Beyond that, are you saying that you would simply commit identical files to no and nb when somebody makes a change on translatewiki? Even if you do that I will still have to do some magic to apply the rails translations to both codes.

comment:7 Changed 8 years ago by Tom Hughes

Resolution: fixed
Status: assignedclosed

I think this is largely fixed now.

Upstream took my fix to the rails translations, so those are now using nb correctly.

At the OSM level we are merging the no translations from translatewiki with the nb transalations from rails and attaching that merged set to both the nb and no codes.

So I think translatewiki can be switched from no to nb whenever you like and things should just work.

Note: See TracTickets for help on using tickets.