CKAN: Ticket #1434: Add i18n strings from extensions

milestone changed

ross — Mon, 28 May 2012 11:15:22 GMT

milestone changed from ckan-v1.7 to ckan-v1.8

status changed; owner set

seanh — Mon, 28 May 2012 11:19:20 GMT

owner set to seanh
status changed from new to assigned

At least for the core extensions, any i18n-able strings should be getting pulled into the ckan.pot file by default.

keywords set

seanh — Mon, 11 Jun 2012 10:44:58 GMT

keywords i18n added

owner deleted

seanh — Fri, 15 Jun 2012 13:40:32 GMT

owner seanh deleted

status changed; owner set

seanh — Fri, 15 Jun 2012 13:46:49 GMT

owner set to seanh
status changed from assigned to accepted

status changed

seanh — Fri, 15 Jun 2012 13:46:59 GMT

status changed from accepted to assigned

status changed

seanh — Mon, 25 Jun 2012 15:39:10 GMT

status changed from assigned to accepted

priority changed

seanh — Mon, 02 Jul 2012 13:48:41 GMT

priority changed from awaiting triage to awaiting merge

Done for the core extensions, pull request: https://github.com/okfn/ckan/pull/47

Perhaps strings from the non-core but officially supported extensions should be added to, but we haven't decided which extensions those are yet, so add another ticket to do that later:

http://trac.ckan.org/ticket/2625

status changed; resolution set

seanh — Mon, 02 Jul 2012 16:18:09 GMT

status changed from accepted to closed
resolution set to fixed