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

Re: Translation question

From: Lübbe Onken <luebbe.tortoisesvn_at_googlemail.com>
Date: Wed, 21 Jan 2009 11:49:14 +0100

Hi Stefan^2,

Simon Large wrote:
> In this case a simple solution might be to include the brackets, so
> "(copy)" instead of "copy".
>
> "Copy source only" might be better as "Copy created from here" or
> simply left without a label.
>
I like Simon's suggestion. Drop the "copy source only" tag. Maybe I miss
something here, but it doesn't provide me with additional information.
At least in my revision graphs, the copy source is directly next to the tag.

Include the action into brackets, so you can remove the brackets from
the formatting string.

BTW shouldn't a "renamed" object display the "Copy from" information as
well?

I also have a problem that the combination of colours and hint texts
doesn't make sense to me in some cases. See attached screen shots
1) "All revisions" are shown:
A branch that has been renamed in r2314 gets a blue node and the
"rename" tag -> sounds good
It contains deletions and renames in r2315, gets a red node colour and
the tag "modified" -> sounds good, but why red? Because "delete" is the
strongest action? But the branch still exists?!?

2) "All revisions" are turned off:
The same branch now gets a red node in r2314 with the "rename" tag in
the hint. -> Doesn't make sense to me.

Cheers
- Lübbe

--
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net  PGP Key ID 0x23F511AB
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=1040857
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].


revgraph1.png revgraph2.png
Received on 2009-01-21 11:49:29 CET

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

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