[FM Discuss] CLI

TJB tjb.olpc at gmail.com
Thu Apr 30 09:24:21 PDT 2009


This manual is another very clean one.  Very, very few typos, but
since it was written by various authors, it is a worthwhile exercise
for me to "standardize" the text: examples of commands in code format
("<code>...</code>"); filenames and directory names in italics;
keyboard keys in bold; double quote marks instead of apostrophes in
text (not in examples!); etc., i.e., copy-editing as Andy Oram
suggested a while ago.

It's taking me longer than I expected, but I will finish standardizing
it. I have finished 24 of 44 chapters so far.

Marcelo, I don't want to hold you up on your Spanish translation
effort.  The vast majority of the changes I'm making are in format,
not content.  If you subscribe to get changes to the manual, you will
see my changes if you are running ahead of me.  I am working the
chapters in sequence.

Tom


 On Sun, 2009-04-19 at 01:33 -0400, TJB wrote:
> Ed, Andy and Adam, I will start editing the manual for format and
> consistency.  With about 40 chapters, it may take up to a week, I
> reckon.  I'll start Sunday.
>
> Tom Boyle
>
>
> On 4/18/2009 6:00 AM, Andy Oram wrote:
>> Now that we're in less of a rush, I agree somebody should copy-edit the book. I'm probably too close to the material now. Maybe on Sunday I can proof the Glossary, though; thanks so much for taking responsibility for it, Ed. I'm not sure I'll have time for the Glossary because I'm leaving on Monday for a week-long trip.
>>
>> Andy
>
>> ----- Original Message -----
>> From: Edward Cherlin <echerlin at gmail.com>
>> To: FM Discuss <discuss at lists.flossmanuals.net>
>> Sent: Sat, 18 Apr 2009 04:14:56 -0400 (EDT)
>> Subject: [FM Discuss] CLI
>>
>> I finished adding items to the CLI glossary. I deliberately did not
>> include terms specific to a particular editor or scripting language,
>> and well defined in that chapter. Please review my work.
>>
>> I fixed some typos and other glitches, and noticed that the whole book
>> could use a good copy-editing. It is definitely not as clean as the
>> work we did on Circumvention. There are some inconsistent points of
>> style. I don't think I know what they all should be, so I am asking
>> for someone who knows the style to review them. Watch out for spaces
>> at the very beginning of paragraphs. They are an artifact of the
>> software.
>>
>> When we come back to this book, I can see several places where we can
>> improve the presentation, and a number of other commands for possible
>> inclusion.
>>
>> I would do more, but I have two other pressing projects on the OLPC XS
>> school server and on teaching math in Turtle Art through discovery
>> rather than lessons. I sent my iconized no-text TA tiles to Walter
>> Bender, and hope to make them publicly available soon.
>>
>> The chat on the Web site is out. We didn't get anywhere near enough
>> chat during the CLI sprint and its followup, compared with talking
>> face-to-face in an onsite sprint. We didn't have the oversight I
>> thought we needed on getting chapters done and reviewed. When I left
>> off tonight, some of the file status selections seemed to be
>> inconsistent.
>>
> _______________________________________________
> Discuss mailing list
> Discuss at lists.flossmanuals.net
> http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net




More information about the Discuss mailing list