Then, maybe the home page isn’t the place for latest contributions and latest comments, and we should have a dedicated page for that?

よみさんいつもありがとうございます。Pfirsichbaeumchenの言う通り、よみさんの声を聞くと幸せです。

I’m asking you why you want do hide the random sentence.

Then it’s likely what Trang said. We solved that problem on the 26th of May.

Problem solved. You can view it on dev.tatoeba.org now.

What about reversing the order in which sentences are displayed (i.e. newest first)?

Why?

What do you mean by breaking down?

Problem solved. :-)

What makes you think inactive new members registered for this reason? Registering is boring, nobody does that unless being forced to. Maybe they want to contribute but are just unable to use the website, or realize it’s not what they were looking for… it could be any reason.

> These newly-registered members who never contribute anything, but list their languages in their profiles will likely give a false sense of how many contributors of given languages we have.

That’s a different problem: inactive users are included in stats. Anyone can become inactive anytime for any reason.

I added this information in the “About this list” area on the right instead, because it would have got into way when editing list name (by clicking on the title).

Should be fixed.

Thinking again, we can’t use parenthesis to mark furigana if some are used in the sentence itself, such as in #1614313 or #464018.

Ah, that’s right! Well done.

These may be harder to handle because they consist of combining characters.

What about uppercase?

Reading odexed’s message about Russian stress marks, it makes me think it’s a bit like furigana in Japanese: they only appear to disambiguate some readings, otherwise they are normally omitted. In that case, I have no objection to blend non-stressed and stressed marks in search. I would just need a complete list of all the possible pairs of stressed and non-stressed letters. Something like [о́,о] but for all the letters that can have a stress mark.

No.

There are languages (like French for instance) in which diacritics totally change the meaning of the words they are on. It’s like they are different letters. That’s why the search behaves like this.

If you think Russian could benefit from having diacritics ignored, we can tune the search engine so, only for Russian. However, by doing so, we prevent people from searching words with diacritics or without diacritics in particular. So I need to make sure I’m not about to make the search better for you but worse for others.

Let’s say I want to look for sentences containing замо́к (1) but not замок (90). If both are considered equal, I need to manually go through the 91 results to find just a single one containing замо́к. You see the problem? But if there is no practical reason to perform such a search in the first place, then it’s not a problem.

There is also a vertical alignment problem when the text wraps (regardless of zoom). Try to limit the body with width:200px. The furigana overlaps with the text.