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

Sync is not working #114

Open
troyane opened this issue Apr 22, 2022 · 3 comments
Open

Sync is not working #114

troyane opened this issue Apr 22, 2022 · 3 comments

Comments

@troyane
Copy link

troyane commented Apr 22, 2022

Summary

Our simple document project became a whole test suit for GitLocalize. It is a great product, but we've found many problems that interfere with our translation work. Please, help us.

Translations are out of sync. Take a look at:

The Sync button in Project -> Settings doesn't help.

Steps to reproduce

Expect that translation to become updated.

Repository URL

https://gitlocalize.com/repo/7294.

What is the current bug behavior?

  • Automatic Sync is not happening.
  • Manual Sync gives no results.

Translations are still outdated, out of sync:

  • Repository contains files with a complete translation.
  • GitLocalize shows the unfinished translation.
  • Translators can't continue work.

What is the expected correct behavior?

Automated and manual Sync updates GitLocalize translation to have the latest files state. As a result, translators could continue work using GitLocalize.

Relevant logs and/or screenshots

I can't grab any logs. If there is an option to enable logs, I'd gladly do it.

Possible fixes

Have no idea yet. But we are ready to supply any required additional information.
Here is some clue:
ilyaspiridonov commented 9 days ago:

Hi all, we have already figured out that the issue is caused by the footnotes (we parse them incorrectly) - likely affecting both sync and PRs in this case. Working on the fixes, I'm trying to prioritise this internally with our small team, bear with us.

@zbroyar
Copy link

zbroyar commented Apr 22, 2022

Please, take a note. It's important for our work and we are stuck.

@svasilenkov
Copy link

@troyane @zbroyar Thank you for reporting the issue, I've forwarded it to our developers. We'll try to fix it as soon as possible.

@zbroyar
Copy link

zbroyar commented Apr 26, 2022

@svasilenkov friendly bump here. Any ETA on the issue?

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

3 participants