[Qgis-community-team] Fwd: github-transifex integrations key problem

[Richard Duivenvoorde]

FYI

See below, we were busy to check if the new Transifex<->Github
integration [0] could work for Documentation.
Looks like it does not yet fit our use case...

Regards,

Richard Duivenvoorde

[0] https://docs.transifex.com/integrations/transifex-github-integration

-------- Forwarded Message --------
Subject: Re: github-transifex integrations key problem
Date: Wed, 27 Mar 2019 22:35:47 +0100
From: Richard Duivenvoorde <rdmailings at duif.net>
Reply-To: rdmailings at duif.net
To: Anthony Dimitrokalis <support at transifex.com>

On 27/03/2019 21.25, Anthony Dimitrokalis wrote:
> 4. In the new GithubIntegration you want a mechanism to create a
> specific resource slug? Is this correct?.

Yes, That is correct. It would be nice if the user can define his/her
own slug, just as you do when you use the .tx/config file if you use the
tx-client to upload/download sources/translations.

See:
https://github.com/qgis/QGIS-Documentation/blob/release_2.18/.tx/config

where all the parts between: [] are slugs defined by ourselves using a
script [0] taking care of different /-_space replacements:

taking the full path to all the index.po files into account, eg:

[qgis-documentation.docs_training-manual_forestry_index]
for
i18n/en/LC_MESSAGES/docs/training_manual/forestry/index.po
and
[qgis-documentation.docs_training-manual_databases_index]
for
i18n/en/LC_MESSAGES/docs/training_manual/databases/index.po

etc

Regards,

Richard Duivenvoorde


[0]
https://github.com/qgis/QGIS-Documentation/blob/master/scripts/create_transifex_resources.sh



On 27/03/2019 21.25, Anthony Dimitrokalis wrote:
> Hello Richard
> 
> Thank you for contacting Transifex technical support.
> 
> I apologize for the delayed response, but i required the time to
> correctly understand the issue at the hand.
> 
> To summarize:
> 1. You have four files named index.po, each representing a different
> index file.
> 2. They are all on the same branch in github, just in different
> sub-directories.
> 3. Only one of these index.po files is downloaded regardless of the
> github integration used. The expected result would be to have all four
> files downloaded, each with a different resource_slug (what appears you
> refer to as a key)
> 4. In the new GithubIntegration you want a mechanism to create a
> specific resource slug? Is this correct?.
> 
> If this is the case then in its current form then you can't assign a
> specific resource_slug using the new Github Integration. However I like
> this idea and understand its value. Therefore I am informing the
> development team about this improvement. Thank you for helping us
> improve our product.
> 
> Please let me know if I can help you further with this issue.
> 
> Kind Regards,
> 
> 
> --
> Anthony Dimitrokalis
> | Transifex <https://www.transifex.com/>
> Join Our Community! <https://community.transifex.com/>
> 
> How would you rate my reply?
> Satisfaction Rating Icons      
> {#HS:808375220-71867#}
> On Fri, Mar 22, 2019 at 6:35 AM PDT, Richard Duivenvoorde
> <richard at duif.net> wrote:
>> Hi, we are using Transifex to translate our FOSS project
>> https://www.transifex.com/qgis/qgis-documentation/ I'm now testing
>> with a small subset of it: https://github.com/rduivenvoorde/qgisdoc
>> currently I'm testing the new TX-Github integration, but hit an issue
>> we actually also had when creating the .tx/config file some time ago:
>> having a Sphinx-based documentation, to be build to html, several
>> files are named 'index.po' (so the become index.html). It seems
>> Transifex ONLY uses the filename to create the 'resource-key'. We hit
>> the same issue when we created the .tx/config file using a script, but
>> then could choose our own keys, eg:
>> "qgis-documentation.docs_user-manual_working-with-vector_index"
>> [qgis-documentation.docs_user-manual_working-with-vector_index]
>> file_filter =
>> i18n//LC_MESSAGES/docs/user_manual/working_with_vector/index.po
>> source_file =
>> i18n/en/LC_MESSAGES/docs/user_manual/working_with_vector/index.po
>> source_lang = en trans.af =
>> i18n/af/LC_MESSAGES/docs/user_manual/working_with_vector/index.po But
>> in the yaml needed for the integration, it seems there is no way to
>> create the resource name: - filter_type: file file_format: PO
>> source_language: en source_file:
>> source/locale/en/LC_MESSAGES/docs/user_manual/working_with_vector/index.po
>> translation_files_expression:
>> source/locale//LC_MESSAGES/docs/user_manual/working_with_vector/index.po
>> So (see attached tx.yaml) this docs contain like 4 index.po files, but
>> only one of them ends up in the (integrated) transifex project:
>> https://www.transifex.com/qgis/qgisdoc/dashboard/ Another reason to be
>> able to create the same keys as we have now is that it would be easier
>> to instruct language coordinators to move the translations to a new
>> project. Hope this makes sense, today I'll will also be available on
>> irc #qgis on freenode. Or if it is easier to talk, let us skype/zoom
>> or whatever. Regards, Richard Duivenvoorde
>>
>>
>>