If you suspended me for posting sentences with the Amazigh name "Ziri," I find this (and I'm sure that others would also find that) totally unfair given the fact that others give themselves the right to post hundreds of thousands of sentences with the name "Tom."

Again, this is a serious discussion and I'm here to try and find a solution (if there ever can be a solution), not to quabble with those people who have nothing constructive to add to this discussion and whose only goal is to gloat over my suspension. Still, solutions should be reached through true, sincere, transparent, and serious dialogue, not through arbitrary and unjustified measures.

The blocking of Amastan/always accounts is excellent news! Many thanks to the admins for their moderation work.

En tiedä miksi sinut on torjuttu, mutta tietyn nimen (yli)käyttäminen lauseissa kuulostaa erittäin oudolta ja riittämättömältä syyltä, juurikin kun ottaa huomioon Tom-lauseet. rivikäyttäjästä tämä näyttää oudolta. Siksi oletan/luulen, että taustalla on jotain muutakin.

It is slow for me too.

Yes, it's been slow for me too.

Not just slow. Mostly I get the message „Tatoeba is currently unavailable. We are sorry for the inconvenience. You can check our blog or Twitter for more information.”
But nor the blog nor Twitter gives any information. Yesterday I hardly did 10 % of the work I used to do in one day.

There was a little problem indeed! Tatoeba should run smoothly now.

I don't understand, Maaster. I adopt and correct sentences in „my languages” regularly. If an autor unadopts sentences, there is no need to be begged to change them. You can use a simple link to find them all:

https://tatoeba.org/eo/activiti..._sentences/epo

(change "epo" to the code of your language).

It's in the sentences_base file.

I assume you're asking this question because you want to transform the data programmatically (otherwise you could just handle edge cases whenever you encounter them). If my assumption is correct, it might be easiest to look at Tatoeba's own code for Japanese transcriptions. (Note that Tatoeba is AGPL-licensed, in case that's an issue for you.)

The validation code for user-provided furigana is here: https://github.com/Tatoeba/tato...ption.php#L220 but I think it might not apply to those that are generated automatically using MeCab.

The testcases might also be helpful: https://github.com/Tatoeba/tato...onTest.php#L27

If you just want to display furigana using HTML <ruby> tags, our code for that is here: https://github.com/Tatoeba/tato...naTrait.php#L9 To be honest, it's not written in an easily readable manner, but I think what it does is basically to assume without validation that there are at least as many kanji as there are readings, and if there is a kanji without reading (|| or end of list) it will merge it with the preceding kanji until the numbers are equal.

So [Kanji1Kanji2Kanji3|Reading1|reading2] would be equivalent to [Kanji1|Reading1][Kanji2Kanji3|reading2], I think.

this is a technical limitation to not overload the server

Here are ways to see more than 1,000 sentences for a given search, using "advanced search."

1. After seeing the original 1,000 results, "reverse" the order the search results are shown.

2. Try the other ways of sorting sentences, plus their "reverse" searches.

I also wonder if this limit of 1000 sentences is too low.
I use this feature to find recently added sentences (in German) and sometimes the last 1000 sentences don't even cover one day.
The limit doesn't apply to sentences of specific users. Some of them own a huge amount of sentences (> 700000).
Currently, displaying or even re-sorting these is reasonably fast.