This was longtime ago suggested and an issue was opened by gillux.

https://tatoeba.org/en/wall/sho...#message_29315

I've written a demo app that allows searching for translated words. You'd have to install Python and Tkinter and put the script in an empty folder with the setences_detailed.csv and links.csv files. The first time you run it, it takes some time to open the main window because the app needs to load the TSV files into a database. After that, opening the app is fast, but search can be slow depending on the number of arguments.

https://github.com/CangarejoAsu...main/search.py

I realize you can never trust random software you find on the internet, but I leave the code here for those with programming skills, or who know someone with programming skills, to check the code.

Try it with the arguments “cat”, “eng”, “gata”, “spa, por”.

I think your best bet would be to go to the Downloads page. A link to this page ( https://tatoeba.org/en/downloads ) can be found at the bottom of every page. The first item on the page lets you download sentence pairs. You could download an English->German and an English->Romanian file. Then you could use the sentence IDs in the files to help you find sentences that exist in both languages. Depending on your situation, you could do this manually, with spreadsheet functionality, or with a programming language (in which case the Links download might also be useful). I don't think we're likely to provide this functionality from the advanced search page, which is already quite complex.

I've written a demo app that allows searching for translations into multiple languages. You'd have to install Python and Tkinter and put the script in an empty folder with the setences_detailed.csv and links.csv files. The first time you run it, it takes some time to open the main window because the app needs to load the TSV files into a database. After that, opening the app is fast, but search is still relatively slow. I would have to optimize the search query to get a speedup perhaps or divide the TSV files into small tables by language.

https://github.com/CangarejoAsu...main/search.py

> After that, opening the app is fast, but search is still relatively slow. I would have to optimize the search query to get a speedup perhaps or divide the TSV files into small tables by language.

Actually, I just needed to create indices.

That means the sentence is "unapproved."

https://en.wiki.tatoeba.org/art...tences-in-red?

Ursäkta min svorska.

Några röda satser bryter upphavsrätt.

Några är från personer som har skrivat många satser i språk de inte kan.

Your point about a better error message that points to the search help page is a good one. However, I want to respond to this statement:

> Obviously this means I wouldn't expect to get any results because a search string like "-personally" is effectively equivalent to searching for an empty string.

Searching for an empty string should ideally find *ALL* sentences that match the other criteria (such as the source language and/or target language, if specified). The reason that this often results in an error is that it produces too many results, and something in the code is not handling that well. (For what it's worth, the error message in this case is different, but also unhelpful.) As you say, specifying "-personally" should find all sentences that don't contain the word "personally", and since this is a relatively uncommon word (at least compared to a word like "the"), the search is effectively equivalent to searching for all sentences.

If you search for an empty string and specify the "from" language as English and the "to" language as one that only has a few translations from English, like Madurese, you will see a finite number of results and no error.

I agree there is room for improvment in search errors.

The reason for this error is that the search engine we use, Manticore, does not allow searches that contain only negations, that is to say "all sentences except the ones that contain some word". (Actually, newer versions of Manticore do allow such searches but not by default, I assume it is because it may consume a lot of resources.)