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

Run "Validate translations" Automatically after Update from POT File #811

Closed
ravage84 opened this issue Oct 19, 2023 · 2 comments
Closed

Comments

@ravage84
Copy link

ravage84 commented Oct 19, 2023

Context:
We are working with managable-sized translation files for our web application projects based on CakePHP.
The POT files are generated through semi-automated means.
Afterwards, the PO files of the usually 1-4 languages/locales will get updated manually by using "Update from POT file..." in Poedit and then translate the new or changed strings.
To verify the translations are still valid, we often press "Validate translations".

Feature proposal:
I think the manual translation verification could be (optionally) improved by running the validation automatcially after updating the PO file from a POT file.

Rationale:
Automating it could help reduce errors and improve the UX for detecting issues with the translations.
This might not work for everybody or ever project. Thus, it would be sensible to have a configuration option just like showing the statistics after updating from POT file.

grafik

@vslavik
Copy link
Owner

vslavik commented Oct 19, 2023

Updating from POT either doesn't change strings or introduces "needs work" strings only. These are already marked as needing attention and won't be used in compiled files until you un-mark them.

It thus makes no sense to explicitly validate after updating from POT.

@vslavik vslavik closed this as not planned Won't fix, can't repro, duplicate, stale Oct 19, 2023
@ravage84
Copy link
Author

We had situations where the state of the file was broken after the upate form the POT file and it was detected by executing the validation function.
I guess it would have also been detected when one would have tried to save the file after the update but that could be after updating several translation strings in the mean time.

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