Red Hat Bugzilla – Bug 129453
Switching locale for Norwegian bokmÃ¥l
Last modified: 2014-03-16 22:47:11 EDT
Description of problem:
I want to switch the norwegian bokmÃ¥l locale from using no_NO to the
correct nb_NO soon and I wanted to hear what the best way to do this
would be from a distro perspective. In the translations I manage
upstream I'm probably just going to add nb.no to the modules and start
removing no.po as soon as I've verified that the new locale works
correctly, but I don't have the necessary access to Fedora's CVS to do
this myself here.
Could someone run a script to rename/copy the no.po files to nb.po?
Can we live with both for one cycle to get some time to verify that
the new one works?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Does nb_NO work in glibc?
Is no_NO an alias?
Kjartaan - are you willing to do the upstream gnome work? :)
I'll do the GNOME part by adding nb.po as a copy of no.po for now.
I'll remove no.po over the next development cycle when I'm certain
that nb_NO works as planned. I think nb_NO was added as a full locale,
so they're both equal in that sense. You'll have to check glibc to be
Realizing this slipped through at the moment.
The proper steps would be:
1) copy all the po files on elvis
2) fix the i18n-access to allow translator access to nb
3) change the lang-table in anaconda
4) change no_NO in glibc to be an alias (to match upstream)
I'll work on #1.
I'll get #3
nb_NO has been in our glibc-common since version 2.3.3-1, so good to
go there. Here is Jakub's comment:
* Tue Dec 02 2003 Jakub Jelinek <email@example.com> 2.3.3-1
- for the time being, include both nb_NO* and no_NO* as locales
so that the distribution can catch up with the no_NO->nb_NO
Sarah can you please update the translator database to give Kjartan
access to this locale?
And #3 is done as well
Do I need to add something like this to gdm?
diff -u -r1.37 locale.alias
--- locale.alias 3 Aug 2004 23:48:55 -0000 1.37
+++ locale.alias 2 Sep 2004 19:47:38 -0000
@@ -67,7 +67,7 @@
Wouldn't you want that reversed? (To prefer nb_NO...)
Didn't know that there was a preferred order really. I mailed the
maintainer about this earlier today but haven't gotten an answer. I'll
reverse it if that makes sense of course :) I wonder how many other
places there are like this in the distro :-/
I don't know that there *is* a preferred order, but I'd assume that's
why the UTF-8 ones are first.
I still haven't gotten permission to commit for the nb_NO locale it
Kjartan - do you have access now?
I just fixed a bug in anaconda so that it defaults correctly to nb_NO
for the installed system. With this, this should be fixed.
I have gotten access, but I was thrown off by not being able to commit
no.po any longer. I understand that this is not needed anyway so I'm
fine with the current status.
The only thing I know of now is preferring nb_NO in gdm's locale.alias
copy. I commited this upstream, but no release has been made since.
I've also posted a call for tarballs for GNOME 2.8.1, so I'll wait and
see what releases that trigger...
Please open a separate bug for gdm in RH's bugzilla, so we can make
sure we get the fix in even if the new upstream release is late.