Custom Query (2152 matches)
Results (1066 - 1068 of 2152)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2802 | fixed | Need to tweak the JSON formatting of the localisations | aron.carroll | aron.carroll |
| Description |
This is what we need the JSON to look like. Taken from the Jed documentation (http://slexaxton.github.com/Jed/). {
// The empty string key is used as the configuration
// block for each domain
"" : {
// Domain name
"domain" : "the_domain",
// Language code
"lang" : "en",
// Plural form function for language
"plural_forms" : "nplurals=2; plural=(n != 1);"
},
// Other keys in a domain contain arrays as values
// that map to the translations for that key.
// Gettext suggests that you use english as your keys
// in case the key isn't found, and it can just pass
// the value directly through.
// Note: by convention, the 0-index location of the translations
// is never accessed. It's just a thing, I guess.
"a key" : [ null, "the translation", "the plural translations", ... ],
// The plural form string is converted into a function
// and the value that's passed into the gettext call
// is passed into the plural form function. It's result
// (plus 1) is the index that the translation comes from.
// We're using sprintf interpolation on our keys so we can
// then sub in the _actual_ values into the result.
"%d key" : [ null, "%d key", "%d keys" ],
// Contexts are keys that are just prefixed with a context string
// with a unicode \u0004 as the delimiter.
// You can use it for anything. Usually it's just for being content aware
// in some way (e.g. male vs. female, product vs. category)
"context\u0004%d key": [ null, "context %d key", "context %d keys" ]
}
This looks like an appropriate python library to do the formatting. http://pypi.python.org/pypi/pojson/ but I'll leave to your discretion. Finally an API endpoint that returns the appropriate request would save us making requests to the i18n directory. /api/i18n/{locale}
For example if the current url is http://localhost:5000/pl/dataset then the client would request: http://localhost:5000/api/i18n/pl This should return the Content-Type: application/json and a 200 with an appropriate JSON body (this can be the language requested or an appropriate fallback). I think that if the fallback is the default language (in most cases English) then we just return a 204 No Content to save data. |
|||
| #181 | invalid | New 'stats' box on right hand sidebar | rgrp | jwyg |
| Description |
With up to date statistics such as:
Could also be nice to have a more dedicated stats page - with information such as graphs showing rate of packages being added and such like. See ticket:184 |
|||
| #2410 | wontfix | New RDF serialization required VOID vocab for related datasets | ross | ross |
| Description |
Taken from http://lists.okfn.org/pipermail/ckan-dev/2012-May/002218.html A few months ago, the RDF provided when dereferencing a dataset's URI was very useful. It described the datasets using many of the "right" RDF vocabularies (dcterms, void, etc). The RDF that is returned now no longer has these nice descriptions. Instead, it seems to be a mindless transcription of the CKAN record. For example, the older descriptions gave: <http://thedatahub.org/dataset/farmers-markets-geographic-data-united-states>
but now it's simply: <http://thedatahub.org/dataset/farmers-markets-geographic-data-united-states>
My old copies of the dataset descriptions mentioned a "GoLD CKAN 1.0" that was credited for the nicer modeling. Where did that go? Can we get it back? Thanks, Tim Lebo <http://semantic.ckan.net/record/91d2c0de-75a4-4bb6-b260-bc2946e1be8b>
… |
|||
