Drupal Norge

Ah, jeg svarte i tråden på drupal.org. Jeg har litt dårlig tid akkurat i dag, så jeg limer inn svaret mitt derfra, dere får late som dere egentlig leser det på norsk:

The reason that I started this thread is that I looked for the Norwegian Bokmål translation, and found the "nb" project (while the "no" project seemed to be better maintained). Confusing. IMHO we should decide on only two projects, (either nn+nb or nno+nob) and let the other remaining projects (no/nb/nn/nob/nno) present a short explanation and just forward to the correct ones. The selected projects names (say nn+nb) should map directly to the cvs tree (translations/nn and ../nb).

I agree with hansfn:
Thirdly: I'm a little disappointed that you think it's fine that Drupal only has "no" (as default Norwegian language code) and not "nb" and "nn" instead. If you look around, you'll find that many projects (including the "GNU C Library") has gotten this right - why shouldn't Drupal also do the right thing (TM).

We should provide a default and out-of-the-box way of providing Bokmål and Nynorsk. Get rid of the redundant efforts. Let there be a standard way within Drupal to select either Bokmål or Nynorsk as a language.

A common effort is great, of course, but this is easily done by letting the nn and nb projects have the same maintainers, and having them link to each other and coordinate efforts. Nynorsk and Bokmål are, in spite of their equalities, different languages, and should be treated that way.

As an example, on systems I work on efforts have been done to standardize this. In Debian, no_NO has been dropped in favour of nb_NO. The i18n project within Skulelinux uses nn+nb (http://i18n.skolelinux.no/teknisk.html).