Ticket #1434 (closed enhancement: fixed)

Opened 3 years ago

Last modified 22 months ago

Add i18n strings from extensions

Reported by: dread Owned by: seanh
Priority: awaiting merge Milestone: ckan-v1.8
Component: ckan Keywords: i18n
Cc: Repository: ckan
Theme: none

Description

Decide which extensions are important.

Change History

comment:1 Changed 2 years ago by ross

  • Milestone changed from ckan-v1.7 to ckan-v1.8

comment:2 Changed 2 years ago by seanh

  • 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.

comment:3 Changed 23 months ago by seanh

  • Keywords i18n added

comment:4 Changed 23 months ago by seanh

  • Owner seanh deleted

comment:5 Changed 23 months ago by seanh

  • Owner set to seanh
  • Status changed from assigned to accepted

comment:6 Changed 23 months ago by seanh

  • Status changed from accepted to assigned

comment:7 Changed 23 months ago by seanh

  • Status changed from assigned to accepted

comment:8 Changed 22 months ago by seanh

  • 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

comment:9 Changed 22 months ago by seanh

  • Status changed from accepted to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.