menu
Tatoeba
language
Kaydol Giriş yap
language Türkçe
menu
Tatoeba

chevron_right Kaydol

chevron_right Giriş yap

Göz At

chevron_right Rastgele cümle göster

chevron_right Dile göre ara

chevron_right Listeye göre ara

chevron_right Etikete göre ara

chevron_right Ses ara

Topluluk

chevron_right Duvar

chevron_right Tüm üyelerin listesi

chevron_right Üyelerin dilleri

chevron_right Ana diller

search
clear
swap_horiz
search

Menü

Duvar'a dön

User55521 User55521 8 Ağustos 2014, 8 Ağustos 2014 tarihinde düzenlendi 8 Ağustos 2014 15:48:01 UTC, 8 Ağustos 2014 15:48:35 UTC düzenlendi link Kalıcı bağlantı

There was a discussion about UIs in [[#3410618]], so I thought I could submit a wish.

Current Tatoeba UI supports only 1 form of language names, which is a problem when translating into languages where words have several forms. In "French example sentence" and "French" in the language list, words "French" may be different in different languages.

Effectively this means that in the current translations of "French example sentence", Russian has a completely unnatural "Пример предложения, язык французский" (Example sentence, language is French), while Polish has an ungrammatical "Zdanie przykładowe francuski" with "francuski" having an incorrect gender.

Surely we don’t want to have unnatural and ungrammatical sentences in an UI. How can we expect users to submit natural sentences if the site itself uses unnatural ones?

{{vm.hiddenReplies[20116] ? 'expand_more' : 'expand_less'}} cevapları gizle cevapları göster
sacredceltic sacredceltic 8 Ağustos 2014 8 Ağustos 2014 16:11:02 UTC link Kalıcı bağlantı

Good point.
Each UI language element has to be separately identified in Launchpad, the translation tool that is being used to create the different Tatoeba locales.

Some of them are actually used as variables in other UI language elements in that tool, in order to avoid multiple (and possibly conflicting) translations of the same element.
But that was done without consideration for the declination problem you mention, because the persons who did had no notion that these could be declined in other languages than the ones they knew.
So although using variables in UI elements looks smart, at first sight, it should be proscribed, and each UI language element should be translatable separately.

{{vm.hiddenReplies[20117] ? 'expand_more' : 'expand_less'}} cevapları gizle cevapları göster
User55521 User55521 8 Ağustos 2014, 8 Ağustos 2014 tarihinde düzenlendi 8 Ağustos 2014 18:06:44 UTC, 8 Ağustos 2014 18:07:40 UTC düzenlendi link Kalıcı bağlantı

I think ideally there should be a way to treat each variable as an array, and the number of elements in that array should be language-dependent.

E.g., so that I can translate "French" as {[NOM] = "французский", [PREP] = "французском"}. And then so that it could be used in text as "%1 example sentence" => "Пример предложения на %1[PREP]".

{{vm.hiddenReplies[20119] ? 'expand_more' : 'expand_less'}} cevapları gizle cevapları göster
sacredceltic sacredceltic 8 Ağustos 2014 8 Ağustos 2014 18:17:44 UTC link Kalıcı bağlantı

That would indeed be an elegant solution. But I don't think Launchpad enables this. It's a one to one translation, alas...

sacredceltic sacredceltic 8 Ağustos 2014 8 Ağustos 2014 16:45:18 UTC link Kalıcı bağlantı

Ideally, Tatoeba should be developed on a framework that handles internationalisation, with the management of locales, and not rely on an external tool for localisation.

gillux gillux 8 Ağustos 2014 8 Ağustos 2014 20:39:45 UTC link Kalıcı bağlantı

Tatoeba uses gettext to localize text. The problem you describe can probably be solved by using the so-called contexts [1]. This allows to have different translations of the same original string for different contexts. For instance "French" in the context of a language list may have a different translation than "French" in the context of "French example sentences". Impersonator, do you think this would solve the problem?

[1] https://www.gnu.org/software/ge.../Contexts.html

{{vm.hiddenReplies[20123] ? 'expand_more' : 'expand_less'}} cevapları gizle cevapları göster
User55521 User55521 8 Ağustos 2014 8 Ağustos 2014 21:35:10 UTC link Kalıcı bağlantı

> Impersonator, do you think this would solve the problem?

I believe no. Context should be language-dependent (e.g. languages X and Y may have 2 cases; but language X uses case A in strings 1, 2, 3 and case B in strings 4, 5, 6; while language Y uses case A in strings 1, 3, 5 and case B in 2, 4, 6), and gettext doesn't allow this.

Of course, we can create all possible contexts (i.e. 1, 2, 3, 4, 5, 6), but this would mean making the translation extremely difficult.

{{vm.hiddenReplies[20124] ? 'expand_more' : 'expand_less'}} cevapları gizle cevapları göster
gillux gillux 14 Ağustos 2014 14 Ağustos 2014 19:17:34 UTC link Kalıcı bağlantı

I’m thinking about a way to solve this and I’ve explained it into a ticket.

https://github.com/Tatoeba/tatoeba2/issues/404