Review and enable CLDR extension
Closed, ResolvedPublic
Actions

Assigned To

None

Authored By

	Reedy
	Mar 22 2011, 1:25 AM

Description

This is logged as an action item, after noticing it on bug 22984

I've got a reasonable feeling that this would be useful for other places too...

Also for bug 16699, related to babel...

Version: unspecified
Severity: enhancement

Status	Assigned	Task
Resolved	None	T31647 Enable the Babel extension on all Wikimedia wikis.
Resolved	None	T25268 Install the Babel extension on strategy.wikimedia.org
Resolved	None	T17165 Install the Babel extension on sv.wikipedia.org
Resolved	None	T20461 Install the Babel extension on fi.wikipedia.org and fi.wikinews.org
Resolved	None	T27817 Install the Babel extension on ko.wikinews.org
Resolved	None	T16207 Install the Babel extension on nds.wikipedia.org
Resolved	Catrope	T17308 Review Babel extension for deployment on Wikimedia Wikis
Resolved	None	T18699 {{#language:...}} should support variable language output as well as input (CLDR)
Resolved	None	T24984 add local language name to Special:SiteMatrix
Resolved	None	T30176 Review and enable CLDR extension

• bzimport raised the priority of this task from to Unbreak Now!.Nov 21 2014, 11:28 PM

• bzimport set Reference to bz28176.

• bzimport added a subscriber: Unknown Object (MLST).

Please guard the PHP file inclusions against path traversal, like what we now do in the core. You can use Language::isValidBuiltInCode().

Otherwise looks fine. My patch in r84664 should be backported so we will know if there is any performance problem.

r85598 does the path inclusion protection

Is this ok now?

I suspect we can just tag/branch it from the trunk copy to bring this into 1.17wmf1?

OK per Tim, deployed to all wikis by me just now.