Re: Package descriptions and making them better
On Sun, Sep 30, 2001 at 01:03:51PM -0500, David Starner <email@example.com> was heard to say:
> > In general, the guidelines of good (technical) writing should apply.
> > Be clear, be concise, be unambigous, be informative, and be correct.
> > I believe that improving our package descriptions has the potential to
> > greatly improve the ability of users to find what they're looking for.
> > (if nothing else, it'll help people who are trying to build saner
> > categorizations of packages and can't take the time to install
> > every single one)
> For example, avoid indenting lines after the first line in the
> paragraph, and don't indent that line if you provide a blank line
> between lines. (Sorry, but this annoyed me throughout your whole
Touché :-) Too much Scheme programming, I guess..
/-------------------- Daniel Burrows <firstname.lastname@example.org> -------------------\
| Wisdom is one of the few things |
| that looks bigger the farther away it is. |
| -- Terry Pratchett |
\-Evil Overlord, Inc: planning your future today. http://www.eviloverlord.com-/