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

Re: [PATCH] make mergeinfo diagram column headings l10n friendly

From: Branko Čibej <brane_at_wandisco.com>
Date: Thu, 24 Jan 2013 11:40:13 +0100

On 24.01.2013 10:40, Philip Martin wrote:
> Branko Čibej <brane_at_wandisco.com> writes:
>
>> On 24.01.2013 00:42, Andreas Stieger wrote:
>>> Hello,
>>>
>>> I found the following output of "svn mergeinfo" troublesome to localize.
>>>
>>> youngest last repos.
>>> common full tip of path of
>>> ancestor merge branch branch
>>>
>>> 2 6
>>> | |
>>> --| |------------ branches/branch1
>>> / /
>>> / /
>>> -------| |------------ trunk
>>> | |
>>> 5 6
>>>
>>> Would something like this not be better?
>>>
>>> youngest common ancestor
>>> | last full merge
>>> | | tip of branch
>>> | | | repository path
>>>
>>> 2 6
>>> | |
>>> --| |------------ branches/branch1
>>> / /
>>> / /
>>> -------| |------------ trunk
>>> | |
>>> 5 6
>> I agree your suggested layout is easier to translate. However ...
>>
>>> A patch to this effect is attached for consideration.
>>>
>>> [[[
>>> make mergeinfo diagram column headings l10n friendly
>>>
>>> * subversion/svn/mergeinfo-cmd.c
>>> (mergeinfo_diagram): use one line per column heading and
>>> vertical lines, leaving room for l10n
>>> ]]]
>> The patch itself still makes translators deal with the position of the
>> vertical bars. If we're going to change the layout, we may as well make
>> it even easier for translators so that they don't have to worry about
>> positioning, just translating the headings.
> In the past we were considering rotating 90 degrees:
>
> |
> |-2 youngest common ancestor
> |\
> | \
> | |
> - -
> - -
> | |
> | |
> 5-|\ |
> | \|
> | |
> | |
> trunk 6-| |-6 branches/branch1

FWIW, I prefer the current layout to this rotated one.

-- Brane

-- 
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Received on 2013-01-24 11:40:56 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.