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 05:34:03 +0200 (CEST)
  • Message-id: <alpine.LNX.2.00.1304300431370.27450@Telcontar.valinor>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Monday, 2013-04-29 at 20:12 -0500, Rajko wrote:

On Mon, 29 Apr 2013 23:24:56 +0200 (CEST) "Carlos E. R." <> wrote:

I tried, but I'm not that good at social skills.

Hmm ... not sure about that :)
Some days, yes, most of them not, or in other words, does that mean
that we have all this discussion just because you had a bad day with
something like systemd, which is a real imposition for all of us
oldtimers that have to throw away hard work we did in the past and
start learning, almost, from scratch?

The thing is, that this I at least feel this like an imposition from above, but one with which I would have to use to keep contributing; as I don't like it, I can stop contributing. Systemd I also feel as an imposition, but there I'm just a user and have no say at all.


I'm sorry that I did not jump in earlier in attempt to cool down the
argument, but I'm not active translator informed how translation
works. Even now, I'm looking at servers and asking myself what is next
to do if I want to translate some application UI strings. There is few
places where to look, and nothing looks uniform and easy to explain.

https://en.opensuse.org/openSUSE:Localization_guide
is obviously outdated.


Yes, it is outdated. However, it happens that each team is organized differently and they write their own documentation. It is just a fact.

- From the wiki above, you can find a reference to a mailing list, a suggestion to join a language team, and a link to the list of teams. When the team does not exist, contributors drop by the mail list and ask what they can do.

<https://en.opensuse.org/openSUSE:Localization_team>

You can have a look from here to the page of a team. For example, if you click on the Spanish link, you will see that (even if you can not read Spanish) the documentation offered is extensive, several long pages (and some of it also obsolete, I'm afraid).

The French team also has their own page, quite long. Several pages, actually.

The Galician team has a page that is not hosted at opensuse.org.

The German team has their page on the wiki, too.

Some teams do not have a team page.

Etc. And many of the teams have their own mail lists - and I know for a fact that not every translator reads this list we are at now.


The pages of each team are not only written in their own languages; but the contents are also different. And they are different for many reasons: how many wiki writers they have, how up to date they keep it, but most important for this thread, that they often are organized differently.


Thus it is very difficult to write an English documentation page because nobody knows how every team is organized... The English documentation got us all started, years ago. Then we each went our own ways.


For example, there are large teams and small teams (1 or 2 members). A small team does not need an organization tool, they can just do it.



If you are in the mood to help, we can go trough process, documenting
it for new translators, so I can establish base for Croatian as well
another two very similar languages (Serbian and Bosnian) and at the
same time have at least one process documented in English, as a base
for improvements.

As all those languages had some translations, that I can't find anymore
I can run in the same situation as Russian teams, but I hope that we can
straighten this later.

I can try to update or improve parts of the English documentation, time permitting, but I have to guide myself on the Spanish team, obviously (and If I have to duplicate all the Spanish pages, they are a lot). Others can perhaps contribute their different procedures.


But I have to confess that I don't feel much incentive to do it. I don't know if it will be of any use at all because the entire procedure is going to be changed, so why document something that will no longer exist?

(somebody from SUSE asked very recently for a "hangout" to explain
our procedures to some visiting teachers at Nuremberg, and I had
to refuse, for the same reasons basically).


Also, there is a side of the organization which is unknown to me, namely what happens beyond. Ie, how the developers submit the files to be translated, and how they get them back. This is something that Karl does, with probably insufficient help. There are a lot of scripts and procedures to do those things, mostly undocumented.



For instance, this release webyast has not been translated at all, simply because their developers did not provide us with the strings to translate. This has happened on previous releases, there are Bugzillas on that. This time I refused to write again another Bugzilla, and I believe nobody else did.

So, no translation for webyast. It has been later removed from our tree.

And believe me, I'm hurt with this situation. I have translated the whole of webyast to Spanish since they started, and I feel frustrated that I could not translate the current 12.3 release :-(

(It is my understanding that they are going to use weblate from now on. I hope them success. Really.)

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

iEYEARECAAYFAlF/O7oACgkQtTMYHG2NR9X0ZwCeMPWU37dwdVs+DKE8fKokSNDJ
w90AmgK2U0FmrLwR+lapCmA4ySX/rxfq
=Fm+U
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-translation+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-translation+owner@xxxxxxxxxxxx

< Previous Next >