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

Thu Jul 22 11:48:10 PDT 2021

There is no synchronization:
[image: image.png]
Compare with:
 Has the Integrations tab, and clicking on it, its synchronized with
contents of develop branch
[image: image.png]
[image: image.png]

Before: when we didn't have this, we had to manually push
the workflow was something on the lines of:
tx push -l en
<translate on transifex the changed strings>
tx pull -l es

Some time ago, we have it set to once a file is translated, then
automatically make a PR, as you can see in this PR
https://github.com/pgRouting/pgrouting/pulls?q=is%3Apr+is%3Aclosed+label%3ATranslation
all the ones that are with a title like: Translate
'/locale/en/LC_MESSAGES/pgr_boykovKolmogorov.po' in 'es'

But now that all files are translated we have the setting to make the PR
when the file is 100% reviewed, because that is not the case yet
I manually have to do
tx pull -l es
Verify that there is no sphinx syntax error and fix if any in transifex,
pull again.
until there is no error, and then I push and make a PR that contains all
the recent translations.

So for example in OSGeoLive I changed one time 500 strings in Japanese
because of sphinx syntax, and the ones that were reviewed, I un reviewed
them
so a Japanese person could check that I didn't mess up the Japanese while
fixing syntax (try to not be your own reviewer)

On Thu, Jul 22, 2021 at 1:24 PM Esteban Zimanyi <estebanzimanyi at gmail.com>
wrote:

> The problem as I see in Transifex is as follows. I currently have two sets
> of files fully synchronized for English and Spanish. I continuously add a
> new function to MobilityDB and I write the documentation in English.
> Transifex should work with diffs and keep the previous translations so only
> the few lines of documentation corresponding to the new function should be
> marked for translation.
>
> On Thu, Jul 22, 2021 at 8:05 PM Vicky Vergara <vicky at georepublic.de>
> wrote:
>
>> 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
>>
>>
>> _______________________________________________
>> 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/f4d358ee/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 14352 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/mobilitydb-dev/attachments/20210722/f4d358ee/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 34653 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/mobilitydb-dev/attachments/20210722/f4d358ee/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 12619 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/mobilitydb-dev/attachments/20210722/f4d358ee/attachment-0005.png>