Re: [readthedocs] internationalization support ?
- Michael Bayer
- 2012-01-21 @ 23:09
On Jan 21, 2012, at 5:43 PM, Eric Holscher wrote:
> Yea, it's on the short list of things to do. I want to get rid of the
whole whitelisting thing first, as that leads to 99% of the support
requests, and makes the user experience suck for new users. I have a
branch to do this, that just needs a little more love to get into prod.
are you or anyone sprinting at Pycon on RTD ?
> After that, internationalization is the next big feature on the list,
and is def. the most requested. It seems like it won't be too hard, we
just need to figure out if we want to automagically figure out what
languages you have, and build them all, or let users select them somehow,
kind of like versions now.
I'd vote for automatic. If someone went through the effort to put the
.po/.mo/whatever files for a specific language into the project, they
should want all those to be built. I haven't tried it yet but it sort
of seems like Sphinx does it this way in any case.
> On Sat, Jan 21, 2012 at 1:56 PM, Michael Bayer <firstname.lastname@example.org> wrote:
> Hi -
> just curious if/how RTD plans to support Sphinx internationalization,
i.e. that described at http://sphinx.pocoo.org/intl.html.
> Ideally if my project had .po (or .mo? ) files checked in to a directory
pointed to by locale_dirs, I'd get
myproject.readthedocs.org/<language>/latest for each language, right ?
> Eric Holscher
> Engineer at Urban Airship in Portland, Or