Menu
I just translated/added #7899917 but I forgot to select Turkish, so my Turkish sentence was saved as an English sentence. I then brought up my sentence again and attempted to edit it. I tapped on the English flag icon and changed it to the Turkish flag icon and saved it. It appeared to have worked but if I search for "less than half" (eng-->tur), I see my Turkish sentence still marked as an English sentence.
(Normally I don't translate to Turkish, but this one was too obvious to pass up.)
my guess is that the search engine had to scan again the corpus and save your language change, so, initially, it recognized your sentence as English, then, when it updated, it recognized this sentence as Turkish
CK changed it for me.
But isn't this a bug, though? I know there's something about not every user having the permission to delete sentences, but I would think that if users are allowed to add new sentences (including translating sentences), they should at least have the permission to edit and delete their own new sentences (including the associated language flag icon), at least before they get permanently added to the database? (I notice that newly translated sentences are displayed in light grey.)
Here are the steps to reproduce this bug:
1. Do a search from English to X to get some results on the page.
2. Pick a sentence and tap on the translate icon.
3. The language dropdown and flag icon should show English. If not, change it to English.
4. Add the translation in language X. Save it.
5. Do the exact same search. Your newly translated sentence should appear in the results but it's language flag icon would show English instead of language X.
6. Tap on the grey arrow on the left of your newly translated sentence to select it.
7. Tap on the edit icon to edit your sentence. Change the language flag icon to X. Tap Save. The language flag icon appears on the screen as though the save was successful.
8. Do the exact same search again. Your newly translated sentence again appears incorrectly with the English language flag.
then I think it's related to this issue that has already been reported: https://github.com/Tatoeba/tatoeba2/issues/1678