-
Notifications
You must be signed in to change notification settings - Fork 0
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
Inverted question mark flagged in Spanish #246
Comments
Once you start widespread validating of languages other than English, I expect that you'll find MANY things like this. I have ensured that the language_code is carried through to most places it's needed, so you can either just suppress the warning notice for non-English languages, or else implement language-specific punctuation checks. (So I personally would mark this issue as an enhancement, not a bug.) |
Thanks for the insight. Helpful!
…On Sun, Jan 16, 2022, 11:05 PM Robert ***@***.***> wrote:
Once you start widespread validating of languages other than English, I
expect that you'll find MANY things like this. I have ensured that the
language_code is carried through to most places it's needed, so you can
either just suppress the warning notice for non-English languages, or else
implement language-specific punctuation checks. (So I personally would mark
this issue as an enhancement, not a bug.)
—
Reply to this email directly, view it on GitHub
<#246 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJ2ZXPG3FYZBXJDTNGA7YLUWOIRJANCNFSM5MBEWSOQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
The problem is that when translators see any of these errors even the lowest priority warnings, they are reacting strongly to them. We have set the validation level to High by default and yet we still get editors who are pouring over each issue no matter how insignificant. Until we have a validation interface that is integrated directly into the editing process we are delaying teams every time we increase the precision of the validation. It may be useful to have this warning above, and others like it, as a potential feature for others to develop in the future, but we’re unequipped to track the potential punctuation issues for each language with any consistency (probably even for English). I think spell checking libraries would be better at this than we ever will be. I wonder if these type of issues should be regulated to a priority number that is designated for punctuation issues that are language specific that are ignored by default. |
... at the beginning of a question. Should not be.
The text was updated successfully, but these errors were encountered: