French documentation

[ccomb]

Here is an exhaustive french translation of the documentation (even with the API).

We currently have a sphinx build which is generated using this buildout and automatically updated by these builders using this configuration

[coveralls]

Coverage remained the same at 80.07% when pulling e2c8b1f on anybox:french-doc into 6686fd3 on OCA:8.0.

[coveralls]

Coverage remained the same at 80.07% when pulling e2c8b1f on anybox:french-doc into 6686fd3 on OCA:8.0.

[lmignon]

:%s/an consumer/a consumer

[lmignon]

👍 Thank you @ccomb!!!

[ccomb]

I'm adding a short text in the contribute page to explain how to maintain a translation

[guewen]

Wow, what a massive work!
Thanks @ccomb 😍

[guewen]

Following these steps, python bootstrap.py gives: Error: Couldn't open /tmp/tmp/buildout.cfg. We have to download odoo-connector.cfg to buildout.cfg before with wget https://bitbucket.org/anybox/public_buildbot_buildouts/raw/tip/odoo-connector.cfg -O buildout.cfg.

[guewen]

Maybe repeat this step here not to miss it:
Addthis patch https://bitbucket.org/shimizukawa/sphinx-intl/pull-request/9/`_ to sphinx-intl (until merged) to support fuzzy translations`

[guewen]

@ccomb According to you, what is the better way to publish the french version on odoo-connector.com?
One way I think of is to push it to a /fr subfolder and add a link on the index page saying something like "this documentation is also available in french" directing to /fr.

[gurneyalex]

just wow!

[guewen]

Would your builders be able to push the docs on odoo-connector.com (considering it would have access rights) and would you agree to push the builds there? Currently this is a manual process, I git add, git commit and git push the new builds in the repo: https://github.com/camptocamp/openerp-connector-docs (we can move the repo if required) (then the pages are automatically served by GitHub pages).

[ccomb]

@guewen the 'fr/' subfolder is a good idea, since sphinx is still not able to natively host several translations, indeed the index page should provide a list of the available translations pointing to the correct url.
I think our buildbot is capable of uploading the build to a different url, because the upload is just the step 20 of the builder, whose configuration is public and the destination URL is visible in the configuration. Just need to cross-check with @gracinet

[gracinet]

On 04/21/2015 12:06 PM, Christophe Combelles wrote:

I think our buildbot is capable of uploading the build to a different
url, because the upload is just the step 20
http://buildbot.anybox.fr/builders/connector-postgresql-9.4/builds/7
of the builder, whose configuration is public and the destination URL
is visible
https://bitbucket.org/anybox/public_buildbot_buildouts/src/b1ac741276c21316b20faf1a9372bbcdf605b0c2/MANIFEST.cfg?at=default#cl-16
in the configuration. Just need to cross-check with @gracinet
https://github.com/gracinet

@ccomb, yes, it is, details are here:
http://docs.anybox.fr/anybox.buildbot.openerp/current/apidoc/anybox.buildbot.openerp.subfactories.postbuildout.html?highlight=sphinx#anybox.buildbot.openerp.subfactories.postbuildout.sphinx_doc

[gracinet]

@guewen previously I had only @comb latest comment on-hand, so I thought it was only a matter of subpath… There's no uploading of any kind currently from our buildmaster to another server (we're cheating, so to speak), but I could add a special step to that effect.

I've never hooked such a bot to GitHub, so if there's a better way than creating a full-blown user account, please tell me

[guewen]

I've never hooked such a bot to GitHub, so if there's a better way than creating a full-blown user account, please tell me

A user account for pushing the changes you mean? I think that's the way to go.

[guewen]

@gracinet @ccomb I'm currently investigating the build of the docs from Travis

[guewen]

Let get it merged and I will complete #60 to build the french doc as well and include the links.
Thanks again @ccomb