Mailinglist Archive: opensuse-translation (94 mails)

< Previous Next >
Re: [opensuse-translation] Managing SUSE translations in unified way
  • From: "Carlos E. R." <carlos.e.r@xxxxxxxxxxxx>
  • Date: Tue, 30 Apr 2013 06:09:27 +0200 (CEST)
  • Message-id: <alpine.LNX.2.00.1304300537180.27450@Telcontar.valinor>
Hash: SHA1

Content-ID: <alpine.LNX.2.00.1304300607410.27450@Telcontar.valinor>

On Monday, 2013-04-29 at 19:21 -0500, Rajko wrote:
On Mon, 29 Apr 2013 15:48:37 -0300 "Gabriel [SGT]" <> wrote:

I can't help but feel insulted by this thread, everything I read is an
attack to the tool I developed.

Problem is that Tomáš probably searched for tools, did not find yours
so he could not see that there are some translations. After he did
some work to provide web based translation tool and proudly announced
that there is now centralized server for all openSUSE translation

What he found out is outright rejection with very little to no
information how current process is working. I doubt that Tomáš did not
try to search mail lists, but without knowing exact name of translation
server, I would be surprised that he found anything.

But why did he not ask us first? The mail list is published in the list of mail lists at opensuse. Or even ask in the general mail lists where to find the translators. People now and then come and ask us to translate things, so we are findable.


We would have been very happy to explain our procedures and this would not have happened.

Instead, we suddenly find out that our existing procedures and tools are going to be replaced. First news. Not asking us, just doing it.

Are you really surprised of the rejection? :-o

The only reason for the existence of Vertaal was to provide a way to
organize a task, that otherwise, would be a mess. Vertaal born in
2009, replacing a previous tool also developed by me, named POAT.

A basic documentation for users exists that's all (no, you
won't find it in google, all robots are disabled)

As you may noticed, if it would be accessible by Google, then
translation list would, most likely, not see whole this discussion
that showed how easy is to break community project.

Maybe it is just not possible to have it accesible by google. :-?

One bad day for one vocal contributor, when he expects that everyone
know what he knows, probably spiced with problems to learn and debug
new system components, that creates an argument with people willing to
give their time to openSUSE project, just as you do, and we have cracks
in a community.

True. :-(

It was meant for
openSUSE only, that's the reason it doesn't support (yet) git, and
because I don't want to host all the space required for git. I didn't
want to sell it for anything else but openSUSE.

I know someone created the project in transifex, so, there is another
tool too, why don't we use transifex instead (which for me is very
very similar of what I could see of weblate)
someone is Margerite, that is contributing to openSUSE, and most likely
she did not find Vertaal too.
there is only Russian translation active. As there is Russian
translation of Factory in Vertaal, it seems that they don't communicate
among themselves quite well.

Notice that vertaal is not a translation tool. It is a team organization tool, and an easy interface to download and submit the files we translate. It does not serve to edit and translate strings, that is done with standard tools like poedit, lokalize, kbabel, even emacs.

Each team chooses to use it or anything else they prefer.

There was a suggestion to introduce weblate and move to git. I'm not
against that, the only thing I'm against it's the branch merging, if
that is optional, I'm good. I can't even stop wasting my money
maintaining the Vertaal VPS.

I don't see why is branch merging a problem. I'm not active as
translator, so I have no idea why merging may present a problem. If you
have some example to help understanding.

Well, for example some teams voted to keep the translations from SLES and openSUSE separate. We do not want their strings.

Then, a file might be translated differently from one version to the next. Ideally, a file is translated whole by a single translator so that the language is uniform. This can break if you move strings from one version to the next.

Of course, this is only my very personal opinion.

We all express our opinion.


- -- Cheers,
Carlos E. R.
(from 12.1 x86_64 "Asparagus" at Telcontar)
Version: GnuPG v2.0.18 (GNU/Linux)

< Previous Next >