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

_______________________________________________
Mailman-i18n mailing list
Posts: [email protected]
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-i18n/archive%40mail-archive.com

Reply via email to