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 Loading a PO File #812

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

Run "Validate translations" Automatically after Loading a PO File #812

ravage84 opened this issue Oct 19, 2023 · 3 comments

Comments

@ravage84
Copy link

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.
Sometimes, the PO files will get updated by search/replace in our IDE instead of though Poedit.
To verify the translations are still valid, we often then open the PO file and press "Validate translations".

Feature proposal:
I think the manual translation verification could be (optionally) improved by running the validation automatcially after loading the PO 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

Poedit does, in fact, perform validation after opening a file.

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

It might but the results aren't shown (as a window or see #815) and depending on how one has setup the entry sort order potential errors aren't shown in the visible part of the list of translation strings.

grafik

grafik

grafik

grafik

@ravage84
Copy link
Author

The warning could be shown after load only if there are (severe) issues like duplicated entries.

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