Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Order of translations seems random #404

Open
Guite opened this issue Feb 9, 2020 · 6 comments
Open

Order of translations seems random #404

Guite opened this issue Feb 9, 2020 · 6 comments

Comments

@Guite
Copy link
Contributor

Guite commented Feb 9, 2020

This could be related to #398 but I am not sure about that.

We've setup a GitHub Action workflow which should regularly extract translations and create a pull request for adding missing messages.

But it seems that the order of messages in a catalogue is changed every time.
Maybe it would be possible to change that in order to use a "fixed order" instead?

Here is an example: zikula/core#4123
If you look at the diff you'll see that it moves messages around which did not change actually.

@odolbeau
Copy link
Member

I tried on my local installation but I don't have this problem.
In my case, with loco, everything is fine, I can download translations several times, the generated translation file will always be the same.

I guess it depends on the adapter you're using?

@Guite
Copy link
Contributor Author

Guite commented Feb 10, 2020

I guess it depends on the adapter you're using?

That would be Filesystem then.

@odolbeau
Copy link
Member

Which command is used during this automatic PR? Is it translation:download or translation:update.
Could you please give a try to both of them to see if you have the same problem?

(May be linked to #392)

@Guite
Copy link
Contributor Author

Guite commented Feb 10, 2020

We use translation:extract.

@Guite
Copy link
Contributor Author

Guite commented Feb 10, 2020

@odolbeau
Copy link
Member

which should regularly extract translations
Obviously, it was already said! ^^

Looks like it's definitively the same issue described in #398.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants