You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
Hello @zeke! Our devs looked into this issue. The problem will disappear if you change Part of Speech to Noun
Currently it is related to machine learning that responsible for highlighting all terms and we can't influence on that part directly. It will some time to train our system to do it better. Hope for your understanding 🙂
The text was updated successfully, but these errors were encountered:
I'm started from the answer above, it's the change "part of speech" to noun what's the normal way to play around this bug. This works not ideally, but how I'm saying this good way to play around this.
What's next?
I start investigating how we upload this glossary, we use crowdin-glossary module, what's makes this easy. And I add the ability to set part of speech. And it's should work yes, is not it? But not.
Why it's not working?
It's doesn't work because API does not know about part of speech. You can see the answer from Crowdin Support Team below:
Hello,
For now, the only way to import Glossary with the part of speech is by using UI upload.
But I believe it's a great improvement idea, so I have already shared this information with >our developer's team!
And once we get any news on the matter, we will immediately let you know!
Thanks for bringing this to our attention :)
This has only one way to upload a glossary, its use UI, it's not that way what's I want because we upload this on every release.
So, what's exits?
How solution we can upload this glossary once with part of speech and wait until the Crowdin team doesn't make this possible with API, I have already patched version of crowdin-glossary what's can do this.
In this example,
a
is being highlighted likeapp
:Mitigation advice from Crowdin's @v3ctorman
The text was updated successfully, but these errors were encountered: