Hello, It shouldn't be a completely new translation, only an improvement (in our opinion). In the current version, there are not-translated segments, false translations, mistakes in grammar and orthography and maybe mistakes in the consistency. Our work will include a lot of quality assurance and an increasement of the accessability...the second part is more important...a little example: No one here (neither me) has known, what "bounce processing" is (its actually translated with "Bounce-Erkennung"). Now, i know what it is...but i had to read in wikipedia. You know what i mean? We think, its possible to found everytime a term in the target language to explain for everyone, whats exactly meant. mtaenigma On Fri, 12 Oct 2012 22:04:38 +0200, Federico Leva wrote:
I wrote this answer by mistake thinking I was on mediawiki-i18n mailing list. It's offtopic on the list but maybe it will be interesting for you nevertheless! (Mailman devs are thinking about using translatewiki.net and are waiting for feedback from translators.)
mta_enigma, 11/10/2012 13:12:
We (some fellow students and I) come from germany and study software localization at Anhalt University of applied science. We have to work on a lokalization project for our studies.
Hello and welcome, glad to hear you're willing to work on MediaWiki localisation.
Yes, we know that there is still a german translation. however we have found some mistakes in it and in some cases, it is hard to understand for people, who don't work very often with the computer (for example elderly people). We want to create a version with more accessability based on the current german version.
I'm not sure what you're asking here, but I suggest to work on the existing translation; creating another fake language like de-formal is not a good idea IMHO. After registering on translatewiki.net, you can review the existing translations, also with its quality assurance tools,[1] [2] and propose the changes which you find necessary to your fellow translators,[2] if necessary by building a structured glossary.[3] Only if it proves impossible we can think of other ways.
Nemo
[1]
<https://www.mediawiki.org/wiki/Help:Extension:Translate/Quality_assurance> [2] For core:
<https://translatewiki.net/w/i.php?title=Special%3ATranslate&taction=proofread&group=core&language=de&limit=5000&task=acceptqueue> [3] On https://translatewiki.net/wiki/Portal_talk:De [4] https://translatewiki.net/wiki/Terminology
Am 17.10.2012 12:56, schrieb mta_enigma: Hi "mta enigma", as I am the maintainer of the German translation I already sent you a long reply to your private mail to me last week. Unfortunately, your mailadress has been broken and mails to your adresses have been undeliverable.
<mta_enigma@mail.cloudin.de>: host mail.cloudin.de[94.127.16.116] said: 554 5.7.1 <mta_enigma@mail.cloudin.de>: Relay access denied (in reply to RCPT TO command)
Feel free to contact me directly, but please provide me working mailadresses or phone numbers. Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin
On Mit, 2012-10-17 at 11:56 +0100, mta_enigma wrote: [...]
example: No one here (neither me) has known, what "bounce processing" is (its actually translated with "Bounce-Erkennung"). Now, i know what it is...but i had to read in wikipedia. You know what i mean? We think, its
Didn't you understand the word as such or didn't you know the concept? If it's the first, which word did you know? If it's the second, no German word wouldn't have helped either.
possible to found everytime a term in the target language to explain for everyone, whats exactly meant.
First, no you won't. E.g. I failed to find a good translation for "scheduler" (to name the oldest one I can remember) for decades. And no, I do not know (or have) the legendary "Siemens-Dictionary" from the times where German was the corporate language there. The examples from that "Siemens-Dictionary" at the university were quite funny at that time. Second, you loose all the techies who know the English terms and who have to learn(!) the - new and thus artificial - German word. And for people who do not know what "email bounces" (as such) are, a new German word won't help either (or an existing word with the n+1. meaning). And yes, IMHO the french strategy to define French words purposely different from the English one for new terms is a strategic failure - at least for the IT area. Third, it may help the few who do not speak English at all but it doesn't help the ones who - sooner or later - find the Internet and will learn the original English ones. Bernd PS: I'm purposely ignoring the problem with the whole bunch of German regional dialects (and even .at has far more then one. Yes, most in .de can't distinguish them, though they are quite different) which adds to the problem of an "official German translation". We already have way too much "German language imperialism" in .at - thanks to strange TV translations;-) -- Bernd Petrovitsch Email : bernd@petrovitsch.priv.at LUGA : http://www.luga.at
On Oct 17, 2012, at 01:28 PM, Bernd Petrovitsch wrote:
PS: I'm purposely ignoring the problem with the whole bunch of German regional dialects (and even .at has far more then one. Yes, most in .de can't distinguish them, though they are quite different) which adds to the problem of an "official German translation". We already have way too much "German language imperialism" in .at - thanks to strange TV translations;-)
It is possible to support sub-dialects. We already support pt and pt_BR for Portuguese and zh_CN and zh_TW too. I've occasionally been asked for English dialects to add colour and internationalisation :). What doesn't work so well right now is stacking those dialects, so that if most of en_US works for you, you'd just need an en_GB for the few differences between American and British English. This might be something we could fix in Mailman 3; it could make for a nice little contribution if someone were interested in doing so. -Barry
participants (4)
-
Barry Warsaw -
Bernd Petrovitsch -
mta_enigma -
Peer Heinlein