http://localhost/ticket/2802 <p> This is what we need the JSON to look like. Taken from the Jed documentation (<a class="ext-link" href="http://slexaxton.github.com/Jed/"><span class="icon">​</span>http://slexaxton.github.com/Jed/</a>). </p> <pre class="wiki">{ // 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" ] } </pre><p> This looks like an appropriate python library to do the formatting. <a class="ext-link" href="http://pypi.python.org/pypi/pojson/"><span class="icon">​</span>http://pypi.python.org/pypi/pojson/</a> but I'll leave to your discretion. </p> <p> Finally an API endpoint that returns the appropriate request would save us making requests to the i18n directory. </p> <pre class="wiki">/api/i18n/{locale} </pre><p> For example if the current url is <a class="ext-link" href="http://localhost:5000/pl/dataset"><span class="icon">​</span>http://localhost:5000/pl/dataset</a> then the client would request: </p> <pre class="wiki">http://localhost:5000/api/i18n/pl </pre><p> 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. </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/2802 Trac 0.12.3 toby Mon, 06 Aug 2012 13:03:53 GMT http://localhost/ticket/2802#comment:1 http://localhost/ticket/2802#comment:1 <ul> <li><strong>owner</strong> changed from <em>toby</em> to <em>aron.carroll</em> </li> <li><strong>status</strong> changed from <em>new</em> to <em>assigned</em> </li> </ul> <p> @aron </p> <p> I've done most of this </p> <p> to test </p> <p> get strings <tt> python setup.py extract_messages </tt> </p> <p> mangle the zh_TW creates .po/.mo files - I may need to fix plurals <tt> paster trans mangle -c .ini </tt> </p> <p> create .js files only zh_TW will be correct due to other .po/.mo files being 1.7 ones <tt> paster trans js -c .ini </tt> </p> <p> /api/i18n/zh_TW should be correct </p> <p> please note we do not have en.js I'm returning {} I think this is the correct response (maybe something else as we should just use the default _('...') strings - maybe we need to do something else </p> <p> for what it's worth pojson does not provide the format you wanted so I adapted it </p> <p> reassign if you need fixes </p> Ticket aron.carroll Mon, 06 Aug 2012 16:10:46 GMT http://localhost/ticket/2802#comment:2 http://localhost/ticket/2802#comment:2 <ul> <li><strong>status</strong> changed from <em>assigned</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>fixed</em> </li> </ul> <p> Cool, this is in as of 8b72d1f8e9ba </p> Ticket