Other country names CLDR provide short names for:

• (what we currently use) → (what we could use instead)
• Bosnia & Herzegovina → Bosnia
• United Kingdom → UK
• Myanmar (Burma) → Myanmar
• Macau SAR China → Macau
• Palestinian Territories → Palestine
• United States → US

Because nobody spent the time to do it yet. There are many things that could be done to improve Tatoeba in various ways, but we’re are focusing our efforts on other things at the moment. By the way, we usually use stars to emphasize, *like this*.

That happened during the process of country names localization. Before, all the countries names were displayed in English regardless of the selected language (on the top-right drop down). Besides, the previous list was geopolitically outdated, so we updated it using a list from the Unicode CLDR repository[1], that also provides translations into many languages. And for some reason, they call it “Hong Kong SAR China” (apparently SAR stands for Special Administrative Region). We can change that name if you want. But if we do, we will also need to update all the translations, which is rather cumbersome.

[1] http://cldr.unicode.org/index/downloads

Edit: CLDR also provides “Hong Kong” as a short name, “Hong Kong SAR China” being the “normal” name. So we may change it along with all the translations.

That’s right.

Sorry, I wasn’t talking about the sentences members contribute and that form the Tatoeba corpus, but the translations of the Tatoeba website itself (which can be viewed by selecting Russian or Belarusian in the top-right drop down). Is it clearer now?

よみさん、また録音してくれて、どうもありがとうございます。すごく嬉しいです。
また「よみさんの声早く聞きたい」（#3137746）です。

またよろしくお願いします！

This issue actually impacts all the languages. Thank you for reporting it. It will be fixed in the next update.

For everyone who is wondering about the Russian (and Belarusian) translations. As tommy_san pointed out the plural rules (the rules that determines what plural case should be used giving a number included in a string such as “{n} members”, and how many cases there are) have been modified. The change was operated by Transifex and I asked them why. They answered me the following:

> We changed the plural forms for Russian and Belarusian recently. We
> had them set to be three and now they are four. We get all the rules
> from unicode.org [1] and as you can see these languages have four
> plural forms at the moment.
> We actually had way too many requests to update the plural forms of
> these languages and that's why we did it.
>
> [1] http://www.unicode.org/cldr/cha...ral_rules.html

If I understand correctly, the update adds a new plural case (the fourth and last one) that handles decimal numbers such as “1.5”. The other cases remain the same as before. However the current implementation of Tatoeba does not support decimals, so you’ll probably never see this last case used on Tatoeba. It should not change anything for us.

But this update actually broke the plurals strings in Russian an Belarusian, so I had to patch our framework to support these new rules. I had little time to test the patch thoroughly, so it may have introduced bugs. If you see anything wrong please point us to a concrete example of a faulty plural, preferably on http://dev.tatoeba.org/ (the reason is that http://tatoeba.org/ changes so frequently that the example may disappear if the numbers change).

As Trang said, I'm working on making transcriptions editable on Tatoeba, which will ultimately allow searching in both scripts for every language we provide transcriptions for. It is still far from being ready to use on tatoeba.org, but I've made good progress recently and I’m confident to say that I’ll complete it at some point. In the meantime, could you point me to a document that describes the transcription rules between Cyrillic and Latin in Serbian?

Also, the Wikipedia page about romanization of Serbian states that “Romanization can be done with no errors, but in some cases knowledge of Serbian is required to do proper transliteration from Latin back to Cyrillic”. Could you tell us more about it?

Do you remember what exact sentences were misrecognized? To my knowledge, the list of languages in your profile has nothing to do with the autodetection feature, which may report and let you effectively add sentences in any other language.

あれ？一級とか一段は最高なので日本人はそういう風に考えると思ってましたけど。言語能力試験にもそうでしょう。

Tu as raison. En ce qui concerne le retour-chariot, je constate ce problème sur Chrome mais pas Firefox. J’ai cherché un peu, mais je n’ai pas trouvé de solution. Ça doit être un bug dans Chrome. Il vaudrait mieux qu’on ajoute un bouton pour copier.

Nice improvement!

> 1) The stats for sentences per language.
> http://dev.tatoeba.org/eng/stats/users_languages

You mean https://dev.tatoeba.org/eng/sta...s_by_language, right?
I personally like the colored bust to represent “admin”, “corpus maintainers” etc. in the column header, but I guess it’s a no-go for colorblinds.
It would make more sense to move the link to show_all_in/<lang> to the sentence number cell, so that you’re brought to the list of sentences when clicking on the sentences number rather than the language name.
Sortable columns would be super useful.

> 2) The stats for the languages of the members, which is a new page.
The title columns “5, 4, 3, 2, 1, ?” are *very* cryptic, I think we should totally change them. The meaning of a number itself is different among languages (for instance Japanese uses 1 for the highest level, while others uses 1 for the lowest level). It’s also confusing because the table mixes cardinal numbers for sentences and ordinal numbers for levels, which are two totally different things yet represented by the same symbol.

Again, sortable columns would be super useful.

Personnellement, je n’ai pas de difficulté pour sélectionner les phrases (à l’aide d’un triple clic), mais je conçois que ça peut être compliqué, notamment sans souris.

Ton commentaire m’a donné une idée. Et si on préremplissait le contenu du champ traduction lorsqu’on ajoute plusieurs traductions à une même phrase ? Concrètement, ça donnerait :
1. Je clique sur le bouton traduction, j’entre une traduction, j’envoie, paf.
2. Je clique à nouveau sur le bouton traduction de la même phrase, et le champ traduction contient ma précédente traduction, dont je peux facilement faire une variante.
3. Je clique sur le bouton traduction d’une autre phrase, et le champ traduction est vide, comme à l’étape 1.

Cela faciliterait ton cas d’utilisation, mais embêterait peut-être d’autres personnes dans d’autres cas ?

Noted.

I can see the problem when viewing the number of Japanese speakers in Russian, when the number of members is 101. The problem comes from the translation of the site into Russian. The string between parenthesis is a so-called plural string, which means it has different translations giving the number (of members). The original English string is "{total} member" when {total} equals 1 or "{total} members" otherwise. The translation may have different variations too, depending on the language and {total}. Russian have more complex plural rules, in which 101 is a different case than 102, and the 101 case translation is wrong.

The problematic string can be fixed here (giving you have an account on Transifex and have been accepted in the Russian translators team): https://www.transifex.com/proje...ource/42114924

Follow this guide to translate on Transifex: http://en.wiki.tatoeba.org/arti...ce-translation and see especially the “Plural strings” section.

You can test how the translation renders by waiting a few minutes and going to http://dev.tatoeba.org/.

Pfirsichbaeumchen wrote recently:

> * Hovering with the mouse over a tag will now show the name of the user who added it.
> * Dynamic button labels that were not localized are localized now.

> Two long awaited changes. Thanks to all who worked on them.
> Zwei lang erwartete Änderungen. Vielen Dank an alle, die daran gearbeitet haben!

You’re welcome. I didn’t know the dynamic buttons localization was such a long awaited change. I fixed it because Guybrush88 brought that topic yet another time, and it took me less than an hour to fix it. To be honest, as a developer I tend to work on things that bugs me personally, or that I feel important, but I have very little idea about the areas regular members would like progress to be made. For instance, recently I’ve been working on improving the autogenerated furiganas and make them editable (it’s still incomplete), but only because I personally care about that.

I’d like to work more on things that matters to members, but I don’t really know. So my question is: how could I?

For those who don’t know, we developers are using Github to keep track of issues and discuss technical side of ideas [1]. At the moment, we have 170 open issues and this number has been stable for the past ten months [2], although we closed a lot of issues (412) (which means we roughly opened as many issues as we closed). Many of these recorded issues are too vague or half-relevant however. Some of us tried to label priorities but they are often quite objective.

[1] https://github.com/Tatoeba/tatoeba2/issues
[2] https://9-volt.github.io/bug-li...toeba/tatoeba2

These are yet to be made translatable however. The ones that got fixed are the OK/cancel buttons of the sentence edit form and the list name edit form.

Thank you, we are aware of this bug already: https://github.com/Tatoeba/tatoeba2/issues/184

Hello Jakov,

We implemented a new feature to allow easy linking of sentences, which probably makes your “Tatoeba visual linker” script obsolete. See this page for more details: http://en.wiki.tatoeba.org/arti.../intro-linking