Mailinglist Archive: opensuse-translation (94 mails)

< Previous Next >
Re: [opensuse-translation] Weblate / posummit status and possibilities
  • From: Tomáš Chvátal <tchvatal@xxxxxxx>
  • Date: Mon, 08 Apr 2013 15:11:40 +0200
  • Message-id: <2111261.a0723uKgK5@bugaboo>
Dne Po 8. dubna 2013 14:42:24, Andrea Turrini napsal(a):
2013/4/8 Tomáš Chvátal <tchvatal@xxxxxxx>:
Dne So 6. dubna 2013 18:14:39, Carlos E. R. napsal(a):
Indeed. I will not work via a web tool, no matter how good it is.

Why is that, if the tool is more convinient to use and easier to manage?

Because for instance I prefer to translate offline and then go online
just for updating/committing.
This is particularly important if you have a time/traffic bounded web
connection, or you translate on spare time when you do not have
internet connection.

We can still allow the write access in the end but you would loose all the

I hope so.

Yep it will work. In a bit i will sent lenghty mail explaining the process.
And you guys will for sure be able to translate the .po files directly.

There will be two ways how to do it. One to download all po files from weblate
and then upload them back up when needed. Other using the git repositories
with the packages and create merge requests on github.

Yes there were some paid translations, but that is not regular basis
afaik, so we can merge and review the "pro" stuff to be merged into
openSUSE and vice versa.

Provided that the po files for SLE and openSUSE are the same. Can you
ensure this? If not, what is the practical difference between keeping
different copies on a web site and keeping them on an svn server?
Moreover, I have seen in the faqs that it is possible to propagate
automatically changes from one branch to others. How do you manage
branches where by choice translations are different (for instance,
because the translation team has agreed for the next release on a
different translation style or on different translation rules)?

It is possible to have the fuzz there, you can decide one branch say Yes and
other Yup, but this allows you to work the other way around too so if you find
some typo in one branch it will be fixed in all (if desired).

Ahem AFAIK the translations are merged anyway and whatever you contribute
to the openSUSE release is marked GPL/CC and others and will one day be
included in next SLE or actually used by anyone else interested.

From my point of view this is different: I am translating for openSUSE
following the translation rules Italian openSUSE translation team has
agreed on.
I care only about the result in openSUSE; I do not care whether these
translations are then used by others (they can, it is GPL/CC); it is
their problem to merge/adapt/rewrite my translations to their needs.
For sure I do not want that my work, done following agreed rules, is
wasted by commits done by translators from different teams following
different translation rules, just because a web tool is considered
more convenient to use and easier to manage.
BTW, the same happens now with the SVN server: I really dislike when
messages from other translations are merged and not marked as fuzzy,
but hopefully this is not happening any more.

Yes automatic merges won't happen, it must be reviewed by translation team
member and you will now see his name on the change so you can blame him via
the web tool. If you decide just to ignore the SLE stuff you of course can but
as it is just matter of few clicks it would be nice to have those in sync.
Even the paid guys could have good ideas :-P


< Previous Next >
List Navigation