Re: Consistent formating long descriptions as input data
On Sun, Apr 26 2009, Stefano Zacchiroli wrote:
> Well, it depends on the goal. Mine was on the line of what I perceived
> it was "consensus" (totally subjective perception), that of trying to
> use a standard language: either Markdown or RST.
This is what I as trying to push towards, and I too thought we
had a rough consensus on it.
> My implementation is for the former, and I tried to avoid supporting
> anything in addition. The only exception I made is to split in place
> But if we have tons of '.' or 'o' lists, for sure we will need to
> break that rule and support them. Do you have numbers about how many
> such lists we have? If they are just a few they can easily be fixed,
> if they are half the archive (which I doubt, having seen them rarely)
> it would be a different story ...
>>>> ,-- count-bullet-chars.sh --
>>>> total=`grep "^ *[-+\*o] " $lists | wc -l`
>>>> for tag in "\*" "-" "+" "o"; do
>>>> items=`grep "^ *$tag " $lists | wc -l`
>>>> percent=`echo "scale=4; $items / $total * 100" | bc`
>>>> echo "Tag $tag was used $items times ($percent%)"
>>>> Tag \* was used 9277 times (68.0900%)
>>>> Tag - was used 3837 times (28.1600%)
>>>> Tag + was used 120 times (.8800%)
>>>> Tag o was used 390 times (2.8600%)
> If nobody from -policy objects, I'll submit it tomorrow.
E = MC ** 2 +- 3db
Manoj Srivastava <firstname.lastname@example.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C