Page MenuHomePhabricator

Messages for no/nb is failing in no.wp
Closed, InvalidPublic

Description

There is defined some messages in no subspace and some in nb subspace, while Translatewiki.net uses nb. In addition both a nb and a no language is defined in the selector at no.wp. This creates a situation where some messages are localized and some are not.

For example will the header of this page fail.

This works
http://no.wikipedia.org/w/index.php?title=Mal%3ACitation&diff=10708724&oldid=9277851&uselang=no

This fails
http://no.wikipedia.org/w/index.php?title=Mal%3ACitation&diff=10708724&oldid=9277851&uselang=nb

Actual failing message is MediaWiki:Difference-title/nb, it is defined in Translatewiki but not locally.

Only one language should be defined in the selector or both should be fully defined as complementary.


Version: unspecified
Severity: normal
Whiteboard: aklapper-moreinfo

Details

Reference
bz37528

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 12:29 AM
bzimport set Reference to bz37528.
bzimport added a subscriber: Unknown Object (MLST).

I'm going to post a query at no.wp about what to do with this as written forms of Norwegian is a little bit touchy.

(In reply to comment #0)

Actual failing message is MediaWiki:Difference-title/nb, it is defined in
Translatewiki but not locally.

Both http://no.wikipedia.org/wiki/MediaWiki:Difference-title/nb and http://no.wikipedia.org/wiki/MediaWiki:Difference-title have content now. I guess this is related to MediaWiki 1.20wmfX lagging up to a few a few weeks with MediaWiki master.

(In reply to comment #2)

(In reply to comment #0)

Actual failing message is MediaWiki:Difference-title/nb, it is defined in
Translatewiki but not locally.

Both http://no.wikipedia.org/wiki/MediaWiki:Difference-title/nb and
http://no.wikipedia.org/wiki/MediaWiki:Difference-title have content now. I
guess this is related to MediaWiki 1.20wmfX lagging up to a few a few weeks
with MediaWiki master.

Jeblad, is this issue still current?

Jeblad, is this issue still current?