Thai doesn't use periods, but I get warnings #622
Unanswered
LibreShawn
asked this question in
Q&A
Replies: 2 comments 2 replies
|
Punctuation is checked here Maybe an additional configuration to exclude some languages from the checks at all would be fine for this? Can you provide a PR for this? |
2 replies
|
The ResourceTableEntryRules is serialized into the settings, actually it has only one data member, which is the However I wonder if adding all this overhead allowing such a detailed configuration for such an edge case is worth the effort, since it has to be tested and then maintained forever. Maybe just turn of all checks for Thai, or a list of configurable languages? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I have a Thai translation of my English strings and I am currently getting 37 warnings for strings that don't end with period. As far as I understand from searching the web, Thai doesn't use periods. Is there a way to turn off specific warnings for specific languages? Or maybe the code should be modified to not flag that warning for Thai.
I have a similar issue with U+2026, the single character ellipsis. If I use that character instead of 3 periods (...) in a Korean translation, it flags it as an error.
All reactions