Ticket #1650 (closed enhancement: wontfix)

Opened 2 years ago

Last modified 20 months ago

Add new language/translation of fields for datasets.

Reported by: ross Owned by: ross
Priority: awaiting triage Milestone: ckan-future
Component: ecportal Keywords: [4d]
Cc: Repository: ckan
Theme: none


Datasets should have a field that specifies the language used in the dataset, this should be a two character ISO 639-1 code (see http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes for list) . Also make sure all tests and migrations are resolved. [2d]

Determine the best approach to having 'translation_of' references to show which dataset the current one is a translation of. This may be a translation of field, or a 'copied from' field or another form of package relationship. [2d]

Change History

comment:1 Changed 2 years ago by ross

Some translations are currently done with full locales (i.e. pt_BR) but we don't also have pt_PT and so where I would normally default to the language if there are only one translation I am unsure what to do in this case.

Currently supports the short language code or the locale code, but this will need to be resolved before we address #1653

comment:2 Changed 2 years ago by kindly

  • Component changed from ckan to ecportal

comment:3 Changed 2 years ago by ross

  • Milestone set to ckan-future

Branch exists for #1650

comment:4 Changed 2 years ago by ross

  • Milestone changed from ckan-future to current-ckan-sprint-2012-06-25

comment:5 Changed 23 months ago by ross

  • Milestone changed from current-ckan-sprint-2012-06-25 to ckan-v1.8

comment:6 Changed 22 months ago by ross

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

Probably not going to do this for ECP as John found a cleaner way of doing it.

comment:7 Changed 20 months ago by ross

  • Status changed from new to closed
  • Resolution set to wontfix

Closed as unnecessary now.

Note: See TracTickets for help on using tickets.