-
-
Notifications
You must be signed in to change notification settings - Fork 958
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
Burmese punctuation not detected #7375
Comments
The full stop is supported in Weblate 4.11: 8e3a19f |
Thank you for your report; the issue you have reported has just been fixed.
|
Hello, This is still not working even though Weblate has been updated to version 4.13.1 |
The upgrade will not trigger running checks, in the default configuration the checks are updated once in a month. You can trigger this manually using updatechecks management command. |
Thank you! |
Hello, It seems Weblate is still picking up these as a full-stop error The problem is weblate is picking up the last 2 lines as a misplaced fullstop even though the source is a question |
- write the question mark as unicode escape sequence to avoid paste error on composing chars - extend test coverage - skip comma check for question mark sentences Fixes #7375
I've fixed these now. It turns out that copy-pasting the composed question mark didn't work correctly and caused some issues. |
Thank you! :) |
Describe the issue
Hello,
While contributing to this project to solve outstanding errors I realized the Burmese punctuation is not being detected properly.
I tried researching but not sure how to fix it
https://translate.jellyfin.org/checks/end_stop/jellyfin/
https://translate.jellyfin.org/checks/end_question/jellyfin/
The Burmese full stop is this:
။
and the question mark is this:
း။
I already tried
Steps to reproduce the behavior
No response
Expected behavior
No response
Screenshots
No response
Exception traceback
No response
How do you run Weblate?
Other
Weblate versions
No response
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: