<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Please go ahead with the change as you see fit, that will give me an idea of how docbook works (I dont know docbook)<br>Everything needs to be ready for scaling, like be ready when another language is added, without any hassle. <br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Note that on FOSS4G I will, in the code sprint, talk about translations on transifex, so hopefully translators are attracted and MobilitiyDB can have an additional language in the future.<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Regards<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jul 22, 2021 at 1:18 AM Esteban Zimanyi <<a href="mailto:esteban.zimanyi@ulb.be">esteban.zimanyi@ulb.be</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div>Independently of the releases, I think there are still two issues</div><div>* Structuring of the code: I would propose to have the directory MobilityDB/doc for the XML files of the English documentation and then have a directory MobilityDB/doc/es for the XML files of the Spanish documentation. Then remove all transifex files that are anyway outdated.</div><div>* Ensuring that the licence check finds the XML files of the Spanish documentation. According to my understanding this is not the case.</div><div>If you agree I can prepare a PR with these changes.</div><div><br></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 21, 2021 at 5:39 PM Vicky Vergara <<a href="mailto:vicky@georepublic.de" target="_blank">vicky@georepublic.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Hi Esteban.<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I dont mind being asked.<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br>In general a release should be handled as follows Thinking on rc release candidates:<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Freeze code (Allows documentation changes)<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Freeze documentation (Gives time to translators to translate)<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Freeze translation (everything is freezed, so make the release)<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">So worry about translation when the documentation is freezed. As code, including build code, is not freezed, anything can happen.<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">So for example, Soon there will be a 3.2.1 release for pgRouting, and that minor (3.2) already has translation, but the documentation will have changes. We dont worry about re-translating a minor so the affected documentation for spanish will be in spanglish.<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">But those changes will be ported to 3.3, and 3.3 will be released on october/november, adding new code will be allowed around August, code fixes will allowed during a month after that, but most work will be focused on reviewing the documentation, translators will have october to translate the new/changed lines. And we will release 3.3 at the end of october beginning of november.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Even that you are in a beta version (I think) there are lots of code changes like in this PR<br><a href="https://github.com/MobilityDB/MobilityDB/pull/83" target="_blank">https://github.com/MobilityDB/MobilityDB/pull/83</a><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">So I wouldn't worry about translation yet.<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Now pgRouting have transifex linked to develop branch. <br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><a href="https://docs.transifex.com/transifex-github-integrations/github-tx-ui" target="_blank">https://docs.transifex.com/transifex-github-integrations/github-tx-ui</a></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">So the files are allways with the latest content.<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">But your repository is quite disorganized still, so it is going to be difficult at this moment in time to set up that automatic feature.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">But we are working on it :-)<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Regards<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Vicky<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 20, 2021 at 8:37 AM Esteban Zimanyi <<a href="mailto:estebanzimanyi@gmail.com" target="_blank">estebanzimanyi@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Una preguntita Vicky.<div><br></div><div>Me di cuenta que los ficheros docbook (xml) de la traducción española del manual no tenían todavía la licencia y tu script/workflow que verifica las licencias había pasado. Entonces seguro que los ficheros están puestos donde no deberían estar. Acabo de integrar un PR añadiendo estas licencias en la rama develop.</div><div><br></div><div>Como sabes bien, la primera version de la documentación en español la hice con Transifex, como tú me enseñaste. Sin embargo, en cada nuevo PR que hago añadiendo una función suplementaria a MobilityDB (la última fue asMVTGeom) no puedo recomenzar el ciclo con Transifex porque empieza de nuevo el proceso de cero y eso requeriría un tiempo imposible teniendo que repetir el trabajo ya hecho.</div><div><br></div><div>Por eso yo mantengo sincronizadas las dos versiones en español y en inglés de la documentación sin pasar por Transifex. En github los ficheros en el repertorio</div><div><a href="https://github.com/MobilityDB/MobilityDB/tree/develop/doc/po" target="_blank">https://github.com/MobilityDB/MobilityDB/tree/develop/doc/po</a><br></div><div>están totalmente obsoletos puesto que datan de la primera vez que utilizé Transifex, aunque los ficheros docbook (xml) en el repertorio</div><div><a href="https://github.com/MobilityDB/MobilityDB/tree/develop/doc/po/es" target="_blank">https://github.com/MobilityDB/MobilityDB/tree/develop/doc/po/es</a><br></div><div>son los que mantengo sincronizados manualmente.</div><div><br></div><div>¿Qué me recomendarías para manejar eso de manera profesional ?</div><div><br></div><div></div><div>Esteban</div><div><br></div></div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><pre>Georepublic UG (haftungsbeschränkt)
Salzmannstraße 44,
81739 München, Germany
Vicky Vergara
Operations Research
eMail: vicky@<a href="http://georepublic.de" target="_blank">georepublic.de</a>
Web: <a href="https://georepublic.info" target="_blank">https://georepublic.info</a>
Tel: +49 (089) 4161 7698-1
Fax: +49 (089) 4161 7698-9
Commercial register: Amtsgericht München, HRB 181428
CEO: Daniel Kastl
<span></span></pre></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
_______________________________________________<br>
Mobilitydb-dev mailing list<br>
<a href="mailto:Mobilitydb-dev@lists.osgeo.org" target="_blank">Mobilitydb-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/mobilitydb-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/mobilitydb-dev</a><br>
</blockquote></div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><pre>Georepublic UG (haftungsbeschränkt)
Salzmannstraße 44,
81739 München, Germany
Vicky Vergara
Operations Research
eMail: vicky@<a href="http://georepublic.de" target="_blank">georepublic.de</a>
Web: <a href="https://georepublic.info" target="_blank">https://georepublic.info</a>
Tel: +49 (089) 4161 7698-1
Fax: +49 (089) 4161 7698-9
Commercial register: Amtsgericht München, HRB 181428
CEO: Daniel Kastl
<span></span></pre></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>