[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-i18n-doc
Subject: Re: kde-i18n-doc Digest, Vol 125, Issue 15
From: R33D3M33R <andrejm () ubuntu ! si>
Date: 2013-08-27 18:50:09
Message-ID: 521CF4E1.8050404 () ubuntu ! si
[Download RAW message or body]
Dne 24. 08. 2013 16:45, pis(e Mr. Phan Anh:
> __________________________________________________
> Subject: Answer to Albert Astals Cid <aacid@kde.org
> <mailto:aacid@kde.org>>
> Composer: Anh Phan
> __________________________________________________
> "That we kick an existing contributor with a proven track of work and
> give you
> all the power? Why would we do that?"
>
> 1. First of all, I would like to thank you for your reply and concern
> about my email to the mailing list.
> I thought this was forgotten.
>
> 2. Secondly, noone is kicked out.
> As I have proposed in the previous email, member for Vietnamese
> Maintainer Group is doing well with his translation progress.
> So, "kicking out" is really a inconvenience for both of Localization
> Group and LeHoang himself.
>
> The point is: we have differences in thinking and sharing vision about
> the translation progress.
> My proposal is: Noone is kicked out. Just adding a different team for
> Vietnamese to the current translation.
>
> When we are doing a project, many different ideas should not be dumped
> over the time, debating is a good way for moving forward. The
> discipline between two sides of a coin is a good decision?
> I think that, each element in translation is worth for hardworking
> both for the maintainers and the translator - in this case (for
> translating).
>
> Someone would say, KDE project has already enough languages for each
> native language, adding another language to the same native language
> just leads to defragmentation of developing process.
> I think that, the more differences happen, the more colorful picture
> we will get.
>
> 3. This replying email just has one goal: replying to you, and making
> my suggestion become clear.
> Nothing more, nothing less.
>
> Thank you again for replying my email for suggestion.
>
> Regards
> Anh Phan.
>
Hello,
I think this is wrong. If you would add another team there would be two
variants of the same translation:
- users would be confused which translation to choose
- since work would be split, the translation progress would not be as
fast as with combined work
- users could choose Style1 as primary and Style2 as secondary
translations, but if the styles would differ, it would be a mess
In the end, nobody would use the translations. Here is what we did for
our localization teams:
-assign a coordinator for each big project: KDE,
Gnome,Firefox,Thunderbird,OOO.org, etc.
-coordinators work together and form translation guidelines: a glossary
with common english -> your_languague translations, write down stuff
that translators should be aware off, use common translation memory, etc.
-everyone can add suggestions to glossary, every month or so there is a
meeting and voting about suggestions
-a common mailing list
-etc.
Since the unification, the translation quality is much better than
before and any translator can switch to another group (Gnome <->
KDE,OOO<->KDE) since the translating style is really similar. If the
coordinators won't cooperate, try to convince them why consistency
matters. I'm sure they will change their mind. Just don't force anything
-> suggesting is much better.
Regards,
Andrej
[Attachment #3 (text/html)]
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><br>
Dne 24. 08. 2013 16:45, piše Mr. Phan Anh:<br>
</div>
<blockquote
cite="mid:CAOQ=rPhe=XgxRtWoUEWouAFA-iY5qRVxB=7H0VgA2eAZV9xZ4g@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>__________________________________________________<br>
Subject: Answer to Albert Astals Cid <<a
moz-do-not-send="true" href="mailto:aacid@kde.org">aacid@kde.org</a>><br>
</div>
Composer: Anh Phan<br>
__________________________________________________<br>
<div>
<div class="gmail_extra">"That we kick an existing contributor
with a proven track of work and give you<br>
all the power? Why would we do that?"<br>
</div>
<div class="gmail_extra"> <br>
</div>
<div class="gmail_extra">1. First of all, I would like to
thank you for your reply and concern about my email to the
mailing list.<br>
</div>
<div class="gmail_extra">I thought this was forgotten.<br>
<br>
</div>
<div class="gmail_extra">2. Secondly, noone is kicked out.<br>
</div>
<div class="gmail_extra">As I have proposed in the previous
email, member for Vietnamese Maintainer Group is doing well
with his translation progress.<br>
</div>
<div class="gmail_extra">So, "kicking out" is really a
inconvenience for both of Localization Group and LeHoang
himself.<br>
<br>
</div>
<div class="gmail_extra">The point is: we have differences in
thinking and sharing vision about the translation progress.<br>
</div>
<div class="gmail_extra">My proposal is: Noone is kicked out.
Just adding a different team for Vietnamese to the current
translation.<br>
<br>
</div>
When we are doing a project, many different ideas should not
be dumped over the time, debating is a good way for moving
forward. The discipline between two sides of a coin is a good
decision?<br>
</div>
<div>I think that, each element in translation is worth for
hardworking both for the maintainers and the translator - in
this case (for translating).<br>
<br>
</div>
<div>Someone would say, KDE project has already enough languages
for each native language, adding another language to the same
native language just leads to defragmentation of developing
process.<br>
</div>
<div>I think that, the more differences happen, the more
colorful picture we will get.<br>
<br>
</div>
<div>3. This replying email just has one goal: replying to you,
and making my suggestion become clear.<br>
</div>
<div>
Nothing more, nothing less.<br>
<br>
</div>
<div>Thank you again for replying my email for suggestion.<br>
<br>
</div>
<div>Regards<br>
</div>
<div>Anh Phan.<br>
</div>
<div>
<div class="gmail_extra"><br>
</div>
</div>
</div>
</blockquote>
Hello,<br>
<br>
I think this is wrong. If you would add another team there would be
two variants of the same translation:<br>
- users would be confused which translation to choose<br>
- since work would be split, the translation progress would not be
as fast as with combined work<br>
- users could choose Style1 as primary and Style2 as secondary
translations, but if the styles would differ, it would be a mess<br>
<br>
In the end, nobody would use the translations. Here is what we did
for our localization teams:<br>
<br>
-assign a coordinator for each big project: KDE,
Gnome,Firefox,Thunderbird,OOO.org, etc.<br>
-coordinators work together and form translation guidelines: a
glossary with common english -> your_languague translations,
write down stuff that translators should be aware off, use common
translation memory, etc.<br>
-everyone can add suggestions to glossary, every month or so there
is a meeting and voting about suggestions<br>
-a common mailing list<br>
-etc.<br>
<br>
Since the unification, the translation quality is much better than
before and any translator can switch to another group (Gnome
<-> KDE,OOO<->KDE) since the translating style is really
similar. If the coordinators won't cooperate, try to convince them
why consistency matters. I'm sure they will change their mind. Just
don't force anything -> suggesting is much better.<br>
<br>
Regards,<br>
Andrej<br>
<br>
</body>
</html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic