Wall (7143 threads)
Astúcias
Before asking a question, make sure to read the FAQ.
We aim to maintain a healthy atmosphere for civilized discussions. Please read our rules against bad behavior.
sharptoothed
1 days ago
marafon
1 days ago
Pfirsichbaeumchen
1 days ago
marafon
3 days ago
felix63
3 days ago
AmarMecheri
3 days ago
Shishir
3 days ago
AmarMecheri
3 days ago
AmarMecheri
4 days ago
deniko
9 days ago

Issues with notification emails
Lately, some notification emails may have not been delivered properly. This is related to the issue reported by brauchinet about posting comments taking unusually long. This issue should now be fixed, but in the mean time some of you may not have been properly emailed about things going on, possibly new comments, new private messages, @ notifications and wall post replies.
Incident timeline:
- started on June 28th 2023 05h UTC
- solved on July 3rd 2023 13h31 UTC
Note that the incident did not affect all notifications in that time span, only some of them. The server logs show that 38 sentence owners potentially missed one or more comment. I will try to address these by sending them a private message. As for other kind of notifications, including notifications to members who also commented on the sentence, private messages, wall post replies and @ notifications, please double check as I cannot really tell who missed what.

Merci Gillux. Très pro, bravo !

ご連絡・ご対応を本当にありがとうございます。確認してみます。

🍎 Tatoeba.org Native Speakers with Native Language Sentences
http://bit.ly/nativespeakers
Find native speakers of languages you are studying and get links to their native language sentences.
Updated: 2023-07-01

Does anyone else notice that adding comments takes unusually long?

Me.

Me too.
I use two open windows for adding.

The problem is not only that it's slow, but sometimes I get time outs, the page says me it's not available, while on the other page I can see, everything is working as it is intended.
The content of this message goes against our rules and was therefore hidden. It is displayed only to admins and to the author of the message.
The content of this message goes against our rules and was therefore hidden. It is displayed only to admins and to the author of the message.

Congrats to the Russian team for the number of sentences passing by!

Köszönöm 😊

The number of Russian sentences (2nd place) is a lot nearer to 1st place English, if you compare the number of native-speaker owned sentences.
94% of Russian sentences are by self-proclaimed native speakers.
937,932/1,000,258
Advanced search limited to native speakers (937,932 occurrences)
https://tatoeba.org/en/sentence...roved=no&user=
80% of English sentences are by self-proclaimed native speakers.
However, this drops to 68% if we don't count the English sentences by one non-native English speaker who rates himself as a native speaker of 5 languages.
(1,447,169 - 212,521)/1,804,219
Advanced search limited to native speakers (1,447,169 occurrences)
https://tatoeba.org/en/sentence...roved=no&user=

Congratulation! 🎊💐

Поздравляю! Хорошая работа! 😊
The content of this message goes against our rules and was therefore hidden. It is displayed only to admins and to the author of the message.

Hi!
After a poor search I mistakingly added #11881475 as a duplicate of #928186.
I am not sure the deduplication script would catch it, as my version uses a common space before the final question mark, but the preexisting version uses a narrow non-breaking space.
My version = "[...] têtes{U+0020}?"
Earlier version = "[...] têtes{U+202f}?"
A few questions:
Does the script currently handle this for French?
Is there a preferred canonical format for French on Tatoeba?
Should a canonical form be automatically enforced (similar-ish to what I assume is done for Unicode normalization) ?
Or would it be better to have the de-deplucation script handle it, when conflicts are created ?
Cheers,

Ah! Found a github a conversation saying it has to be handled manually as of 2019.
https://github.com/Tatoeba/tatoeba2/issues/770
I am fine with my version being deleted,
So in the meantime I edited my version to use the narrow nbsp (not really convenient to input on my browser ^^) so that both versions should have the same checksum. I'll be more careful in the future.
Cheers,

I'm guessing that:
- the deduplication script only recognizes exact duplicates (not duplicates that differ in terms of normal vs. nonbreaking space, and not duplicates that would result from Unicode normalization)
- no one has agreed on a canonical format for spaces before question marks for French
- even if there were such an agreement, no one is enforcing it
This is based on my experience with how difficult it is to reach agreement on such subjects, and how hard it is to find someone to implement them in code. It's also based on the fact that there's nowhere on the Tatoeba wiki that mentions variant-form-aware details about the deduplication script or conventions for spaces before sentence-final punctuation in French.
But if someone can confirm or deny my guesses, please do.

Sanomasi oli totta ranskan suhteen, kun viimeksi kysyin huomattuani monia lauseita, jotka erosivat ainoastaan sanavälin lajin tai olemassaolon osalta toisistaan. Pätenee edelleen.
The content of this message goes against our rules and was therefore hidden. It is displayed only to admins and to the author of the message.
The content of this message goes against our rules and was therefore hidden. It is displayed only to admins and to the author of the message.