I'm completely +1 for serving html (and pdf) docs via CouchDB itself (especially, if we're already have such: couchdb.couchdb.org - just need to setup nicer alias for docs). Just give me db url where to upload the builds and story ends on this (: -- ,,,^..^,,,
On Fri, Jan 17, 2014 at 12:48 AM, Dave Cottlehuber <[email protected]> wrote: > Just a note, there's nothing tying us to RTD other than at the time it > was easiest for us to set up and looks ok. > > We have a full ubuntu VM available, the official couchdb.apache.org > website is backed by subversion, anything is possible. > > A+ > Dave > > > > On 16 January 2014 21:40, Andy Wenk <[email protected]> wrote: >> Jan, thanks for the info :) >> >> On 16 January 2014 13:03, Alexander Shorin <[email protected]> wrote: >> >>> Suddenly, they don't support gettext, but just mapping "other project >>> -> language". This means that we have to make N copies (one per >>> language) of our docs and create same amount of RTD projects. Gettext >>> works differently, preventing copying things and generating html/pdf >>> with the respect of existed translations. >>> >>> I think, we should stay with gettext, but our RTD integration process >>> would be a bit tricky in this case. >>> >> >> First I thought - YAY - but after reading >> http://docs.readthedocs.org/en/latest/localization.html (Project with >> multiple translations) I am asking myself "why?". >> >> Alex, I am completely with you with staying with gettext. Do you have an >> idea how to get that working with RTD? Can you point me to the work >> (branch) you already did? >> >> Cheers >> >> Andy >> >> -- >> Andy Wenk >> Hamburg - Germany >> RockIt! >> >> http://www.couchdb-buch.de >> http://www.pg-praxisbuch.de >> >> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 >> >> https://people.apache.org/keys/committer/andywenk.asc
