[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: rdiff -s
Re: rdiff -s
Thu, 24 Jul 2003 02:59:40 GMT
"Derek Robert Price" <firstname.lastname@example.org> wrote in message
> >>Why not just regex for each pattern or
> >>something predictably more consistent like \d\.[\d.]*\d?
> >and requires a much higher level of sophistication or tool in
> >order to convert CVS's summary into... a summary!
> A summary "suitable for easy processing by other utilities". I still
> don't think reducing a four-case case statement in your shell script to
3 I think.
> a single line justifies fixing the line length of CVS output until the
> end of time. I'd like to see CVS using gettext or the like for multiple
> language support someday and getting fixed line length to translate into
> several languages would be a bear.
Actually, that's the best argument you could possibly have
made in favour of fixing it. The summary shouldn't have
anything that is subject to change in translation. Because
people should be able to write and distribute scripts that
don't require modification when the user users a different
The words should be changed from "removed" to "R" etc.
The output of rdiff (no -s) is a very fixed/standardized
rdiff -s should be likewise standardized. You could argue
that it is already standardized, but English verbiage is a very
unusual standard. It is more common to see a "computer
format" with subsequent English explanation in the manual.
- rdiff -s, Paul Edwards, 2003/07/12
- Re: rdiff -s, Derek Robert Price, 2003/07/15
- Message not available