Hi Donald, Thanks for the pointer to l20n, I hadn't seen it before; as a standard data format for translations it certainly looks much more flexible and nicer to use than gettext! I'm curious about this, though:
On 01/26/2016 12:10 PM, Donald Stufft wrote: > Now, all of the above could be written serverside in Python and not require > anything of the end user's browser. We're currently using L20n.js instead of > something serverside for a few reasons. > > The biggest and most obvious reason is because L20n.js is currently the only > implementation of L20n that exists, so moving to L20n at the server side would > require us to devote time to writing that instead of working on Warehouse > itself. What about https://github.com/l20n/python-l20n ? It's hosted under the same org, so it looks official-ish. Is it incomplete/unstable/untested? (Of course the cache-related and responsive-translations arguments in favor of l20n.js would still apply, so I'm not saying you should use python-l20n, I'm mostly just curious whether it's usable.) Carl
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
