fix: add native mode to tx pushes

[jesmrec]

Current Android translation workflow works in native mode:

https://github.com/owncloud/android/blob/b873be87a807d5b4292a470c1ea606b190994888/.github/workflows/translate.yml#L15

translation-sync.yml considers native mode only for pulling translations from tx, but pushing.

That means, strings added/removed in Android's source file are never reflected and available in tx's UI for translation in any language.

In this PR, push and pull operations work in the same way for every mode.

[DeepDiver1975]

the code change itself looks reasonable and more consistent.

never the less: why is there a native mode? there is only make or not ..... we should change the mode argument to state explicit that there is only oldand make .... or maybe just a bool flag?

[jesmrec]

That was added here:

owncloud/android@2372758

not sure which is the best mode for Android, thinking in pushing (pulling works fine).

[DeepDiver1975]

This was bluntly copied over from the translation-sync repo.... But there is also no trace on the diff between native, make and old

[jesmrec]

Then, is it OK to send old as mode in Android, and check what's going on?

EDIT: old mode uses l10n in some steps, this could affect the final result. I'd go for this PR's approach, at least to give the first try.

[DeepDiver1975]

EDIT: old mode uses l10n in some steps, this could affect the final result. I'd go for this PR's approach, at least to give the first try.

native is basically old + a different sub path ..... for sure to be solved differently with the reusable workflows where the sub path is a parameter ....

[jesmrec]

after checking the owncloudci/transifex image and the l10n script inside:

1. l10n only works with .js and .php files. Not suitable for Android (.xml). Not bad, it won't make changes related with Android...

2. l10n must be executed from a directory named l10n:

my $whereami = cwd();
die( "Program must be executed in a l10n-folder called 'l10n'" ) unless $whereami =~ m/\/l10n$/;

3. If we change the Android caller workflow to use sub_path: l10n, then l10n read/write may run, but tx push and pull would also be executed from that l10n directory. That means the current Android .tx/config in the repository root would no longer be used. We would need to move/copy the .tx/config into l10n/.tx/config and adapt source paths.

Two options on my side:

• Merging the changes in the current PR: minimal changes that will not affect other wfs (no changes in make mode, and old stays as it is) and will help Android not to change stuff.

• Keep the translation-sync workflow unchanged and make changes in Android caller workflow:

  • Change sub_path from . to l10n
  • Add or move .tx/config under l10n/.tx/config
  • Adapt the source and translation paths to be relative from l10n

the second one seems like adapting the stuff to the CI, and it should be in the other way round. I'd go for skipping l10n and using Transifex flow, just adding a source push step.

Any other option/idea/suggestion is also welcome.