[Mobilitydb-dev] Fwd: MobilityDB: Spanish documentation files

[Vicky Vergara]

Please go ahead with the change as you see fit, that will give me an idea
of how docbook works (I dont know docbook)
Everything needs to be ready for scaling, like be ready when another
language is added, without any hassle.
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.
Regards



On Thu, Jul 22, 2021 at 1:18 AM Esteban Zimanyi <esteban.zimanyi at ulb.be>
wrote:

> Independently of the releases, I think there are still two issues
> * 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.
> * Ensuring that the licence check finds the XML files of the Spanish
> documentation. According to my understanding this is not the case.
> If you agree I can prepare a PR with these changes.
>
>
>
> On Wed, Jul 21, 2021 at 5:39 PM Vicky Vergara <vicky at georepublic.de>
> wrote:
>
>> Hi Esteban.
>> I dont mind being asked.
>>
>> In general a release should be handled as follows Thinking on rc release
>> candidates:
>> Freeze code  (Allows documentation changes)
>> Freeze documentation (Gives time to translators to translate)
>> Freeze translation (everything is freezed, so make the release)
>> So worry about translation when the documentation is freezed. As code,
>> including build code, is not freezed, anything can happen.
>> 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.
>> 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.
>>
>> Even that you are in a beta version (I think) there are lots of code
>> changes like in this PR
>> https://github.com/MobilityDB/MobilityDB/pull/83
>> So I wouldn't worry about translation yet.
>>
>> Now pgRouting have transifex linked to develop branch.
>> https://docs.transifex.com/transifex-github-integrations/github-tx-ui
>> So the files are allways with the latest content.
>> 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.
>> But we are working on it :-)
>>
>> Regards
>> Vicky
>>
>>
>> On Tue, Jul 20, 2021 at 8:37 AM Esteban Zimanyi <estebanzimanyi at gmail.com>
>> wrote:
>>
>>> Una preguntita Vicky.
>>>
>>> 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.
>>>
>>> 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.
>>>
>>> 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
>>> https://github.com/MobilityDB/MobilityDB/tree/develop/doc/po
>>> están totalmente obsoletos puesto que datan de la primera vez que
>>> utilizé Transifex, aunque los ficheros docbook (xml) en el repertorio
>>> https://github.com/MobilityDB/MobilityDB/tree/develop/doc/po/es
>>> son los que mantengo sincronizados manualmente.
>>>
>>> ¿Qué me recomendarías para manejar eso de manera profesional ?
>>>
>>> Esteban
>>>
>>>
>>
>> --
>>
>> Georepublic UG (haftungsbeschränkt)
>> Salzmannstraße 44,
>> 81739 München, Germany
>>
>> Vicky Vergara
>> Operations Research
>>
>> eMail: vicky at georepublic.de
>> Web: https://georepublic.info
>>
>> Tel: +49 (089) 4161 7698-1
>> Fax: +49 (089) 4161 7698-9
>>
>> Commercial register: Amtsgericht München, HRB 181428
>> CEO: Daniel Kastl
>>
>>
>> _______________________________________________
>> Mobilitydb-dev mailing list
>> Mobilitydb-dev at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/mobilitydb-dev
>>
>

-- 

Georepublic UG (haftungsbeschränkt)
Salzmannstraße 44,
81739 München, Germany

Vicky Vergara
Operations Research

eMail: vicky at georepublic.de
Web: https://georepublic.info

Tel: +49 (089) 4161 7698-1
Fax: +49 (089) 4161 7698-9

Commercial register: Amtsgericht München, HRB 181428
CEO: Daniel Kastl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mobilitydb-dev/attachments/20210722/5705946a/attachment-0001.html>