Daniel Shahaf wrote on Sun, Feb 05, 2017 at 19:55:15 +0000:
> 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.
> 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.
Further thought about this: it sounds to me like the best way to handle
small changes in long strings (such as 'svn help merge') would be to
present the differences in wdiff3 format, where the '<<<' hunk is in the
local language and the '|||' and '===' hunks are in English.
The wdiff format would see through rewrapping (I routinely use 'wdiff -d'
to review documentation patches; it's a life saver), and the 'diff3'
format perfectly suits the problem of porting "upstream trunk" (English
strings) changes to a "child branch" (localized strings).
(sorry for multiposting)
Received on 2017-02-05 21:52:24 CET