-
-
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
Search against pattern containing Scandinavian characters #6826
Comments
What happened to you? You did test against the expected section! That is a sure indication of overwork. What about that instead? |
I probably misread the report, sorry. Providing links to broken search and to the string which should have been found would avoid that... |
Well, there is no such string in this translation. Can you please share a link to the string which should be found and is not? |
This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you! |
That issue demonstrates that the service works as intended randomly since a target is at this moment found. Not a glory case. Conclude from it whatever you want. |
The issue you have reported is now resolved. If you don’t feel it’s right, please follow its labels to get a clue for further steps.
|
It does not work randomly, did you notice that you are on a different server than before? |
Describe the issue
Searches against patterns containing Scandinavian characters invariably produce null outputs.
I already tried
Steps to reproduce the behavior
Expected behavior
Match found; the presence of the searched pattern shall be attested by searching against tulevaisuudessa.
Screenshots
No response
Exception traceback
No response
How do you run Weblate?
weblate.org service
Weblate versions
4.9
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: