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

[TSVN] Re: Re: Some work for the doc writers

From: Simon Large <slarge_at_blazepoint.co.uk>
Date: 2004-09-29 14:02:59 CEST

"Lübbe Onken" wrote

> "Screenshot name", "Revision_EN", "Revision_DE"
> AddedIcon.png, + , +
> BlameDialog.png, 1.0.8, 1.0.4
> Commit.png, 1.0.4, -
> CommitContextMenu.png, 1.0.6, =
> ...
>

It is more complicated than I thought (ie. I didn't think properly).

> Now when preparing the documentation for the next release, the maintainer
> should go through all the existing screenshots and compare them to the
> current revision. If they are the same, he should just set the number in
the
> matrix to indicate that they still match. If not he replaces them with the
> current one and set the number in the matrix.

A lot more work for the maintainer. How about having an out-of-date marker
instead of a version number. If it is wrong, it has to be replaced
completely, so it does not matter which older version is used. That means
you don't have to go through and change the numbers on every release.

"Screenshot name", "Revision_EN", "Revision_DE"
AddedIcon.png, + , +
BlameDialog.png, @, #
Commit.png, #, -
CommitContextMenu.png, #, =

+ means independent
- means missing
= means same as english
@ means up-to-date
# means out-of-date

Also, if this file is versioned, then Stefan can mark a screenshot as
outdated if he changes the UI for something.

> Is that too complicated? Is that worth the effort?

It is complicated, but I think it would help to keep the docs in sync with
the software.

Simon

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Sep 29 15:11:07 2004

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