CLDR and pt

Only language names are extracted from CLDR, everything else should be correct. We could introduce pt-PT locale, but I don't think we could change the meaning of pt without causing massive outcry.

Nike10:24, 22 November 2009

Let me provide the terms for getting that done:

  • organise a vote on pt.wp that the 'pt' code should use 'pt-br' as default. I would recommend that the vote would at least take a month to allow sufficient input from Portuguese Wikipedians
  • in case of an outcome in favour to using the Brazilian variant, create a request in bugzilla:.

The result of processing the bugzilla: request would be the following:

  • all translations in /pt would be put in 'pt-pt'
  • all source code repositories would be updated - lot of work, but we would do that.
  • 'pt' would be made empty, and fall back to 'pt-br'
  • all current 'pt' special page names, etc, that differ from those in 'pt-br' would be added to 'pt-br' as aliases for backward compatibility.
Siebrand10:39, 22 November 2009

+Mention it in the release notes for everybody else other than Wikimedia projects.

Nike16:42, 22 November 2009

If I understood correctly Nike's input, then the "CLDR pt-PT" -> "MediaWiki pt" mapping is already done correctly in MediaWiki, so no issue there.

As for adopting the CLDR main language thingy in MediaWiki (i.e. having a separate "pt-PT", then fallbacking pt to pt-BR) and Siebrand's terms for getting it done, I don't regard it necessary. It's somewhat silly in itself, and as long as we're clear about what "pt" and "pt-br" mean in MediaWiki, (and we are) we should be fine. Anyone disagrees?

This means that the only open issues here would be:

  • a bug in extension Language Names (Version 1.7.1 (CLDR 1.7.1)), because it maps "CLDR pt" -> "MediaWiki pt" when, in fact, the mapping should be "CLDR pt-PT" -> "MediaWiki pt". If we all agree on this, I can follow it up (any special procedure for that?).
  • any future extensions resorting to CLDR may commit the same mapping error - I'd suggest we deal with that on a case-by-case basis, as they turn up. Anyone disagrees?
Hamilton Abreu22:10, 23 November 2009

Right. I think I may have misunderstood. So the CLDR conversion script needs to have code mapping. Niklas?

Siebrand23:12, 23 November 2009

Will look into it when I have time. (Should be easy to do if anyone wants to hack the code though)

Nike21:33, 24 November 2009

Just to ensure we're in synch, what you guys are talking about will resolve the Language Names extension issue, right? So, I won't need to follow it up independently.

Hamilton Abreu00:03, 25 November 2009

Is it correct now?

Nike09:41, 26 November 2009

Thanks for addressing this, Nike. Well... I'm unsure :-). We have:

  • {{#languagename:pl}} now returns the correct "polaco", so that is certainly fixed.
  • But, on the "Other languages" box, in the "Intro" pages of this wiki, it still says "polonês" (incorrect) instead of the correct "polaco". Could this be due to the chache, perhaps?
  • On the weird side of things, though, in the side bar, under section "Recent changes", there was a change from "Traduções em português" (correct) to "Traduções em Portuguese" (incorrect). It seems to have been reverted to the english language... any idea why?
Hamilton Abreu20:51, 26 November 2009
  • Sidebar's in other languages comes from MediaWiki.
  • Don't know about the translations in ... thing. Maybe the pt-pt data in CLDR only has overrides for the pt translations?
Nike07:14, 27 November 2009

Yes, it should be the case that the pt-PT variation only has overrides, pretty much as all other variations which CDLR does not consider main. So, I guess it needs to be retrieved in the same way as en-GB, de-AT, de-CH, etc. Is that possible?

Hamilton Abreu23:57, 1 December 2009

Would be easier if MediaWiki used the same codes...

Nike06:41, 2 December 2009
 

May I be incredibly pushy here and nudge you a tiny little itsy bitsy bit? Maybe some hack possible?

Hamilton Abreu22:46, 8 December 2009
 

Bump. Is there some way we can address this, as most language names continue to be in English?

Hamilton Abreu21:27, 3 January 2010
 

I'd go for fixing the code discrepancy. That is out of my abilities however.

Nike21:49, 3 January 2010