-
Notifications
You must be signed in to change notification settings - Fork 10
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
Update Weblate to the latest version #626
Comments
This is related to dependencies - I have other stuff on this server and I need to upgrade all at once, which is not that easy (or even possible). Although I have plans to upgrade Weblate to latest version this summer, and since then it should be easier to keep it up to date. |
Okay, nice. Dependencies are indeed annoying, that's why I use Docker. 😄 But thanks for taking care of the update this summer! |
I updated Weblate to the latest version. |
Got a new issue: impossible to search CJK keywords.... 🤧 |
@littlegolden Damn. :/ New Weblate switched to FULLTEXT search from MySQL, so it may work differently than before. Any hints how to improve this? I'm not even sure what is the problem. |
hope this is helpful: ngram Full-Text Parser |
This needs to be done in index definition in Weblate migrations. I'll take a look at this closer this weekend, but I would prefer to not mess up with Weblate source code. Unfortunately Weblate seems to be focused on PostgreSQL and ignores some issues with MySQL. :/ |
@littlegolden I don't have good news for you. While using ngram improved search for Chinese, it also make it completely useless for other languages (or at least for Polish), since it returned a lot of unrelated results. With ngram_token_size=2 searching for "post" returned anything with "po" or "os" or "st", so you get a lot of results not even close to "post". I reverted this change as it brings more harm than good. I would assume that migration to PostgreSQL would improve this, but I'm reluctant to installing another DBMS on this server (I need MySQL for other things). I need to think more about this, maybe this is a good reason to finally move Weblate to Flarum infrastructure. For now you can use a workaround: regular expressions search. While regular expression is now what we need, syntax works reasonably well with raw strings and it does not use fulltext, so we can avoid its limitations. For simple search you can use it as |
gotcha, regex is fine~ |
I created separate issue for search problems: #765 Closing this one, since original issue was solved and Weblate is up to date. |
Currently, the version used on https://weblate.rob006.net/ is Weblate 3.9.1, released on October 28, 2019. As I write this issue, the latest version of the software is Weblate 4.7.1, released on June 30, 2021.
Is there any particular reason to use such an old version and not take advantage of the latest version in terms of security and features? 😉
Thanks!
The text was updated successfully, but these errors were encountered: