Talk:Translator in the following language combinations

Discussion: Meta:Babel#Translation combination boxes --Eleassar ^{my talk} 12:34, 12 August 2006 (UTC)

Capital T in Translator?

"This Translator translates from X to Y"... is there a good reason for using capital T? // habj 20:52, 20 August 2006 (UTC)

Bilingual templates

I have a problem with the bilingual templates ... that is: I don't like them since they get to big and will create a huge mess when we want to use the same templates for all projects (uploading them with the bot). It would mean that basically we would have 200 x 200 = ca. 40000 templates - considering all wikipedia languages + using two languages on the template simply creates double work with the localization of it. The template needs to be created in such a way that we get one template that is valid for all wikipedias - so that on the local wikipedias they only need to localize some subtemplates to get things correctly. Instead of creating double work we should think about how to minimize work and maximize results. Now I know that the objection will be: but we do not translate among all that languages - and there I say: at this moment we do not ... but only having 50 languages to consider we have 50 x 50 = 2500 templates ... I am trying to find a way where wikipedias will need to do things only once and where we will be able to use the translated language names in database format like we have them on WiktionaryZ. Thank you for taking the time. (Posting the same to Babel) --Sabine 13:22, 19 September 2006 (UTC)

I would like to add, if we have bilingual templates, then it means not only that 1) we coordinators cannot understand exactly they means but also that 2) we and many other editors cannot prepare them by ourselves. In this reason I conclude English version is preferable on meta in the view of Transcom members. I cannot force any editor to use English version, but I hereby strongly request you to use the original version. --Aphaia 08:28, 21 September 2006 (UTC)

We don't need 200² templates to create bilingual translators templates for 200 languages. Only one and a few multilingual message templates (I translate from // a-language // to // b-language) in as much languages as needed. And that's all. True multilingualism is not so terrific. Arno Lagrange ✉ 12:11, 21 September 2006 (UTC)

I don't like your proposal, because:

• variables are meaningless for me. I don't know which language it is and also its meaning.
• description is meaningless for me. I don't know in which language it is written.

Arno, I am fed up with your condecence, esperant-centricism and template-fetisism. You haven't hear anyone's complaints and ignored the past discussions. What you promote is not multilingualism but the contrary. You scared other translators and now us, coordinators. I am more than happy if you don't disturb us.

Arno, I once decided to leave this project for your sake. Because I was fed up with your bossy attitude. I state hereby if you don't stop to disturb us, ignore us and contintue your rant, I will ask the Board to ban you from meta editing. --Aphaia 04:44, 26 September 2006 (UTC)

I don't understand why you are now ranting at Arno. He made a serious proposal in order to solve the problem mentioned by Sabine. And what was esperanto-centrist about this proposal? (I know he has been esperanto-centrist on other occasions, but I don't see it here). Anyway, why are you so English-centrist? Marcos 22:20, 10 October 2006 (UTC)

Better a trilingual approach

So as to express what a translator can do, at most 3 languages are needed:

1. The language of the wiki (so it's users understand)
2. The source language (so people needing their message translated can find a translator)
3. The target language (so people demanding to read someone else's text can find a translator)

That is more applicable to the way to find to the place where templates are being used, e.g. category pages, etc. than the templates themselves, but I think, they should not be worse. Technically that could be handled with a set of x+N*y templates (not x+N*N) if the size of data processed by templates were not limited, as a safeguard, in MediaWiki. Maybe the limit allows 250 languages before being hit, I do not know. It depends on template size. --Purodha Blissenbach 14:42, 26 September 2006 (UTC)

I have a different idea. Your mentioning 2nd and 3rd points can be showed with Babel template(s) already in my opinion. I think it makes a sense the categories for this template system have all those languages description, but I don't think it needs all three languages are put on the templates itself, specially the templates contains language codes. And meta is surely a multilingual website though, the working language of Wikimedia Foundation and also of Communications committee is only "English", so there is no harm of English description containing templates. Source language description wouldn't help to seek translators, I guess, since I have experienced frequently to be called for Chinese translation when people misunderstood the text as written in Japanese. And on my side, I cannot distinguish languages written with cylic alphabet, etc. My conclusion: to define the source language, text in that language wouldn't work, and the simpler system with language code will be more assured and efficient. --Aphaia 04:33, 27 September 2006 (UTC)

Although you're trying to explain the opposite, your example of people misunderstanding Chinese for Japanese exactly describes the neccessity of a trilingual approach in the most general case. After all, it's hardly more labour to implement than a bilingual one. --Purodha Blissenbach 19:44, 16 December 2006 (UTC)

Is there a current solution?

So this one is outdated. Is there a new solution to store translator information? Pusle8 (talk) 09:34, 6 January 2016 (UTC)