mint-check-translations emits parsing errors for lone '%' strings and provides no success feedback
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- cli, localization, tooling
Research direction
Reproduce the issue by running mint-check-translations against a Hindi .po file containing msgid "%" and msgstr "%", then trace the parser output and completion behavior. Check how successful validation is reported in the terminal and GUI. Done means lone-percent entries produce no parsing errors and a successful run gives explicit feedback when no issues are found.
Written by the indexing model from the issue text.
Description
While validating Hindi translations with mint-check-translations, I noticed that translation entries consisting solely of a percent sign (%) trigger parsing errors in the terminal:
Error parsing msgid at index 0: string index out of range
Error parsing msgstr at index 0: string index out of range
The entry that triggers this is:
msgid "%"
msgstr "%"
Investigation
I added temporary debug output and confirmed that:
- The checker continues processing after these errors.
- Translation loading and validation complete successfully.
- The progress bar reaches completion.
- The GUI remains open and responsive.
So the issue does not appear to stop validation, but it produces confusing terminal output for what seems to be a valid translation entry.
Additional Observation
When validation completes with no translation issues found, the GUI remains empty and does not provide any explicit success message.
Since the documented workflow involves running the checker from a terminal, the combination of:
- terminal parsing errors, and
- an empty GUI with no success confirmation
can make it difficult to determine whether validation completed successfully or encountered a problem.
(While discussing this with Hindi and Tamil translators, it initially appeared that the translation file contained an error, but further investigation showed that validation completed successfully and the message was only emitted by the parser.)
Expected Behavior
Entries consisting solely of '%' appear to be valid translation entries and could be handled without emitting parser errors.
When validation completes successfully and no issues are found, the tool could provide explicit feedback (for example, a "No issues found" message or similar indication).
Environment
Linux Mint (mint-dev-tools)
Observed while validating Hindi .po translations.
Issue comes from the lone '%' that has come in the translation file
poEdit shows this
The files are loaded successfully though
I have a local reproduction and am currently looking into a possible fix.
- Dominant language
- Python
- Stars
- 33
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linuxmint/mint-dev-tools
-
linuxmint/mint-dev-tools#27 · 1 assignee ·
All issues in linuxmint/mint-dev-tools
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100