[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: translations

From: Stefan Kueng <tortoisesvn_at_gmail.com>
Date: Mon, 6 Feb 2017 20:01:11 +0100

On 05.02.2017 20:55, Daniel Shahaf wrote:
> Stefan Kueng wrote on Sun, Feb 05, 2017 at 15:28:25 +0100:
>> On 05.02.2017 12:21, Andreas Stieger wrote:
>>> On 04/02/17 17:13, Stefan Kueng wrote:
>>>> [...]I'm wondering about the translations of those strings.
>>> Several points on this:
>>> #1 Working with Pootle works well, both ways. There is just a bit of a
>>> coordination effort. That coordination needs to be figured out more
>>> urgently than the actual tool.
>>> #2 Help output in UI strings.
>>> This is A LOT of insane frustrating work. Every time the help output of
>>> a command changes even a little bit, the complete string needs to be
>>> re-checked. It needs to be adjusted for spacing and justification. And
>>> at that point you really need to walk the svn code history to adjust the
>>> translation, there is no way to get a stable community of translators on
>>> that level.
>> What does that have to do with my suggestion of using a web based tool or
>> otherwise make it easier for translators?
> You identified a problem (translations don't happen) and suggested that
> changing the translators workflow would fix it. Andreas identified
> a frustrating aspect of the translation workflow that would not be
> addressed by moving to Transifex or Pootle or whatnot. That's perfectly
> on topic to your underlying concern.

Not really. I didn't say that changing the workflow would fix the whole
problem, but make it easier for translators to even start.
The problem Andreas identified is there whether we make it easier for
translators to get started or not.

> That is: perhaps what stops people from translating is the set of
> strings we give them, rather than the format we present them those
> strings in.

And here's the problem: we don't even give them the strings to
translate! They have to install many tools to even get those strings in
the first place.

So I suggest we first come to an agreement on how to provide the strings
to translators without having them create those themselves, then in a
next step maybe set up a web based tool and *then* discuss on how to
help translators with issues like indentation.

If we start discussing everything at once, I fear we'll get nowhere again.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net
Received on 2017-02-06 20:01:19 CET

This is an archived mail posted to the Subversion Dev mailing list.