<div dir="ltr"><div>Hi,<br></div><div><br>Readthedocs suppose to duplicate your source content for each language.<br>It does no deal with i18n support. You can see at <a href="https://github.com/rtfd/readthedocs.org/issues/139">https://github.com/rtfd/readthedocs.org/issues/139</a>.<br>
To illustrate,for exemple, opendatamanual mentionned in the issue is always not working with i18n <a href="https://readthedocs.org/search/project/?q=opendatamanual">https://readthedocs.org/search/project/?q=opendatamanual</a><br>
</div><div>Moreover, the docs seems to confirm too <a href="https://read-the-docs.readthedocs.org/en/latest/localization.html" target="_blank">https://read-the-docs.readthedocs.org/en/latest/localization.html</a><br>
</div><div>So I don't think it's the best although I think it's perfect for "one language" project.<br>I would prefer Travis if possible by using Github hooks.<br><br></div><div>Cheers<br><br></div>
<div>Thomas Gratier</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-04-07 17:49 GMT+02:00 Daniel Morissette <span dir="ltr"><<a href="mailto:dmorissette@mapgears.com" target="_blank">dmorissette@mapgears.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+1<br>
<br>
Daniel<div class="HOEnZb"><div class="h5"><br>
<br>
On 14-04-04 4:55 PM, thomas bonfort wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
PSC,<br>
<br>
In light of the recent projectsvm downtime and the (increasing, given<br>
the new translations) load we are putting on that server while<br>
building our docs, I would like to propose that we transition our<br>
build process to use travis-ci for the compilation part.<br>
<br>
In clear, docs would be automatically built on <a href="http://travis-ci.org" target="_blank">travis-ci.org</a> once a<br>
commit is pushed on the stable or master branch, and would then be<br>
scp'd/rsync'd to the public projectvm directory on success.<br>
<br>
Advantages:<br>
- no need to maintain build scripts on the projectsvm<br>
- the actual travis config files are simple and minimal:<br>
<a href="https://github.com/tbonfort/docs/commit/1d178ab6e6d0765adfbb0fea40404a6a1803a969" target="_blank">https://github.com/tbonfort/<u></u>docs/commit/<u></u>1d178ab6e6d0765adfbb0fea40404a<u></u>6a1803a969</a><br>
(without the logic to publish to <a href="http://mapserver.org" target="_blank">mapserver.org</a> yet, though)<br>
<br>
Inconveniences:<br>
- we rely on an external service we have no control on. we can always<br>
switch back to the current solution if needed (no <a href="http://www.mapserver.org" target="_blank">www.mapserver.org</a><br>
downtime, the docs would just not be in sync while we transitioned).<br>
- building the PDFs has a non-negligeable impact on build times and<br>
apt packages needed to be installed on the travis instances. They<br>
would therefore be disabled by default, but might be enabled on a<br>
case-by-case basis if the commit message contains a magic keyword.<br>
- it might seem we are loosing control as to what is published on the<br>
<a href="http://mapserver.org" target="_blank">mapserver.org</a> website (given the resulting website is automatically<br>
published). In practice this is more or less already the case with the<br>
automatic builds happening on the projectsvm.<br>
<br>
I've had confirmation from the travis team that we are not abusing<br>
their system by implementing this:<br>
<br>
==============================<u></u>==============================<u></u>=======<br>
Hey Thomas,<br>
<br>
Thanks for getting in touch and checking with us!<br>
<br>
We absolutely don't mind you using our service to build and push your<br>
documentation site, quite the opposite.<br>
<br>
We're always happy to see people adopt Travis CI in unexpected and new<br>
ways, so by all means, ship it!<br>
<br>
Cheers, Mathias<br>
<br>
--<br>
Mathias Meyer<br>
==============================<u></u>==============================<u></u>=========<br>
<br>
Before investing more time on this, I will need a go from the PSC. I'm<br>
going to be offline next week and unable to respond, but will start<br>
the transition at my return if no -1s are casted.<br>
<br>
+1 Use Travis-ci platform to build and publish mapserver website<br>
<br>
best regards,<br>
thomas<br>
______________________________<u></u>_________________<br>
mapserver-dev mailing list<br>
<a href="mailto:mapserver-dev@lists.osgeo.org" target="_blank">mapserver-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/mapserver-dev</a><br>
<br>
</blockquote>
<br>
<br></div></div><span class="HOEnZb"><font color="#888888">
-- <br>
Daniel Morissette<br>
T: <a href="tel:%2B1%20418-696-5056%20%23201" value="+14186965056" target="_blank">+1 418-696-5056 #201</a><br>
<a href="http://www.mapgears.com/" target="_blank">http://www.mapgears.com/</a><br>
Provider of Professional MapServer Support since 2000</font></span><div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
mapserver-dev mailing list<br>
<a href="mailto:mapserver-dev@lists.osgeo.org" target="_blank">mapserver-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/mapserver-dev</a><br>
</div></div></blockquote></div><br></div>