<html><body bgcolor="#FFFFFF"><div>Inkscape manual on FM has its own style guide linked from FM. I will set this facility up for all new manuals and send link</div><div><br class="webkit-block-placeholder"></div><div>Adam</div><div><br>This is probably sent while in transit<div><br class="webkit-block-placeholder"></div></div><div><br>On Jul 10, 2008, at 5:44, "Anne Gentle" <<a href="mailto:annegentle@gmail.com">annegentle@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>Hi Joshua,<br>Not sure where to put this but it can get outta my email and into the wiki somewhere. Here are the guidelines my professional editor gave me while she reviewed the OLPC manual:<br><br><span style="color: black;">General terminology observations:</span> <div style="margin: 0in 0in 0pt;">
<span style="color: black;"> </span></div> <div style="margin: 0in 0in 0pt 0.25in; text-indent: -0.25in;"><span style="color: black; font-family: Wingdings;"><span>-<span> </span></span></span><span style="color: black;">You do use both <i>the <span>XO</span></i> and <i>the <span>XO</span> laptop</i>. For simplicity, you could probably just use <i>the <span>XO</span></i> in most cases. </span></div>
<div style="margin: 0in 0in 0pt 0.25in; text-indent: -0.25in;"><span style="color: black; font-family: Wingdings;"><span>-<span> </span></span></span><span style="color: black;">After first using <i>portable USB storage device</i>, use <i>USB device</i>. Don't use <i>USB stick</i>.</span></div>
<div style="margin: 0in 0in 0pt 0.25in; text-indent: -0.25in;"><span style="color: black; font-family: Wingdings;"><span>-<span> </span></span></span><span style="color: black;">Use consistent capitalization when talking about <span>XO</span> Activities. I suggest capitalizing it, which you do most often.</span></div>
<div style="margin: 0in 0in 0pt 0.25in; text-indent: -0.25in;"><span style="color: black; font-family: Wingdings;"><span>-<span> </span></span></span><span style="color: black;">Don't use <i>view</i> and <i>page</i> interchangeably. Use <i>view</i> to refer to the different <span>XO</span> interface. Use <i>page</i> when you are sending the users out to the Internet (as in
<i>web page</i>). Also, use a consistent capitalization for <i>view</i>. You might want to capitalize it, like you do <i>Activities</i>. </span></div> <div style="margin: 0in 0in 0pt 0.25in; text-indent: -0.25in;"><span style="color: black; font-family: Wingdings;"><span>-<span> </span></span></span><span style="color: black;">I would suggest using a consistent verb, <i>click</i>, for telling the users what to do with their pointer on the screen. Don't use <i>choose</i> or <i>select</i>. </span></div>
<div style="margin: 0in 0in 0pt 0.25in; text-indent: -0.25in;"><span style="color: black; font-family: Wingdings;"><span>-<span> </span></span></span><span style="color: black;">You might consider creating a glossary for the book. It would be a good start for a translation glossary. I would include <i>USB storage device</i>, <i>Activity</i>, <i>View</i>, <i>network</i>, <i>mesh network</i>, <i>Give 1 Get 1 (G1 G1)</i>, <i>antennae</i>. </span></div>
<div style="margin: 0in 0in 0pt 0.25in; text-indent: -0.25in;"><span style="color: black; font-family: Wingdings;"><span>-<span> </span></span></span><span style="color: black;">Use <i>network</i>
only as a noun and adjective, not as a verb (one rule of writing for
translation is to use a word as only one part of speech; you would
especially not want to use a word as both a noun and a verb).</span></div><br>As for overarching style that Floss could adopt, I like simplicity. <br><ul><li><p style="border: medium none ; padding: 0pt;">Write well, quickly, in the active voice and the present tense.</p>
</li><li>
<p style="border: medium none ; padding: 0pt;">Put punctuation outside the quoted material.</p>
</li><li>
Place periods at the end of bulleted list items.<br></li><li><p style="border: medium none ; padding: 0pt;"><span style="font-family: Wingdings;"><span></span></span>Replace semicolons with periods.</p>
</li><li>
<p style="border: medium none ; padding: 0pt;"><span style="font-family: Wingdings;"><span></span></span>Use numerals for all numbers below ten. For numbers above ten, spell out the number.</p></li><li>When in doubt, refer to <i>Read Me First! A Style Guide for the Computer Industry</i>, by Sun Technical Publications.</li>
</ul>Let me know if this guide matches what you had in mind, and where it could be housed. <br>Thanks,<br>Anne<br><br><br><div class="gmail_quote">On Wed, Jul 9, 2008 at 3:59 PM, adam hyde <<a href="mailto:adam@flossmanuals.net" target="_blank"><a href="mailto:adam@flossmanuals.net">adam@flossmanuals.net</a></a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">hi,<br>
<div><br>
> 1) We should have a suggested style-guide page on flossmanuals. This<br>
> project would be a good opportunity for us to start adding to that.<br>
> The rule of copyediting isn't "correctness" but "consistency." I'd be<br>
> happy to help in style guide development as I have experience in doing<br>
> this.<br>
<br>
</div>This would be wonderful. Would you feel like taking the lead in getting<br>
this style guide together? I am sure Anne has some ideas on it already<br>
also.<br>
<div><br>
<br>
><br>
> 2) I would suggest we have a project lead/Editor that helps to<br>
> determine if we've met the necessary goals we want to reach in a<br>
> timely manner. Not a dicator, but someone who can help steer help<br>
> toward things that are most in need of being finished. Specifically,<br>
> it would be good if we could mark pages/sections as "needs rewriting,"<br>
> "needs copy-editing," "needs graphic," etc. A good way to<br>
> annotate/bug-track.<br>
<br>
</div>We are almost finished with a basic status marker for workflow<br>
management of chapters. Should be ready tomorrow.<br>
<div><br>
><br>
> 3) It would be good to have the option of going to print. To do that,<br>
> there are a number of print-quality requirements, such as picture DPI<br>
> and other things. We should have a list of technical requirements<br>
> needed to allow for that option in the future.<br>
><br>
<br>
</div>We have a beta system in place for producing print ready source for<br>
print on demand. I will send a url when its ready for a peak. It<br>
utilises CSS3 for formatting print ready book source from FM...the final<br>
result looks beautiful. if you are dying for a look at the beta I am<br>
happy to send anyone a preview url.<br>
<font color="#888888"><br>
adam<br>
</font><div><div></div><div><br>
<br>
<br>
> -Josh<br>
><br>
> On Wed, Jul 9, 2008 at 12:34 AM, Brian Jordan <<a href="mailto:brian@laptop.org" target="_blank"><a href="mailto:brian@laptop.org">brian@laptop.org</a></a>><br>
> wrote:<br>
> On Tue, Jul 8, 2008 at 7:08 AM, Christoph Derndorfer<br>
> <<a href="mailto:e0425826@student.tuwien.ac.at" target="_blank"><a href="mailto:e0425826@student.tuwien.ac.at">e0425826@student.tuwien.ac.at</a></a>> wrote:<br>
> > Greg Dekoenigsberg schrieb:<br>
> >><br>
> >> On Tue, 8 Jul 2008, Walter Bender wrote:<br>
> >><br>
> >>> I can participate if it is in the second-half of August...<br>
> I have lots<br>
> >>> more material from when I made the "getting started" guide<br>
> sitting on<br>
> >>> the "cutting room floor".<br>
> >><br>
> >> I think it's worth considering making this and pitching it<br>
> to O'Reilly. In<br>
> >> the same format as Karl Fogel's "Producing Open Source<br>
> Software" and other<br>
> >> works: available for sale, but freely licensed.<br>
> >><br>
> >> The creation of a physical artifact that can be purchased<br>
> in stores is "a<br>
> >> big deal" and would go a long way towards establishing<br>
> credibility and<br>
> >> permanence. "Holy crap, Sugar must be for real -- they're<br>
> selling the book<br>
> >> in Barnes and Noble! With a Live CD!"<br>
> ><br>
> > That's an excellent idea and I think it would be great to<br>
> make a Live-CD and<br>
> > Sugar documentation available to the masses! :-)<br>
><br>
><br>
> This is a fantastic idea. A publication with step by step<br>
> activity<br>
> creation instructions and a liveCD with the barebones<br>
> activities<br>
> (templates?) referenced in the publication would provide a<br>
> distinct<br>
> starting point for developers interested in our project, even<br>
> those<br>
> who don't have an XO yet.<br>
><br>
> I'd be more than willing to help with pyGame/OLPCGames<br>
> instructions/templates--I've been working through this sort of<br>
> activity creation process all summer.<br>
><br>
> Cheers,<br>
> Brian<br>
><br>
><br>
> >><br>
> >> "Make no small plans." Daniel Burnham. :)<br>
> >><br>
> >> --g<br>
> >> _______________________________________________<br>
> >> Its.an.education.project mailing list<br>
> >> <a href="mailto:Its.an.education.project@lists.lo-res.org" target="_blank"><a href="mailto:Its.an.education.project@lists.lo-res.org">Its.an.education.project@lists.lo-res.org</a></a><br>
> >><br>
> <a href="http://lists.lo-res.org/mailman/listinfo/its.an.education.project" target="_blank"><a href="http://lists.lo-res.org/mailman/listinfo/its.an.education.project">http://lists.lo-res.org/mailman/listinfo/its.an.education.project</a></a><br>
> >><br>
> ><br>
> > --<br>
> > Christoph Derndorfer<br>
> > Co-Editor<br>
> > OLPCnews, <a href="http://www.olpcnews.com" target="_blank"><a href="http://www.olpcnews.com">http://www.olpcnews.com</a></a><br>
> ><br>
> > _______________________________________________<br>
> > Its.an.education.project mailing list<br>
> > <a href="mailto:Its.an.education.project@lists.lo-res.org" target="_blank"><a href="mailto:Its.an.education.project@lists.lo-res.org">Its.an.education.project@lists.lo-res.org</a></a><br>
> ><br>
> <a href="http://lists.lo-res.org/mailman/listinfo/its.an.education.project" target="_blank"><a href="http://lists.lo-res.org/mailman/listinfo/its.an.education.project">http://lists.lo-res.org/mailman/listinfo/its.an.education.project</a></a><br>
> ><br>
><br>
><br>
><br>
><br>
> --<br>
> Joshua Gay<br>
> [m: 617.966.9792 irc: jgay twitter: joshuagay]<br>
> Free Software Foundation, campaigns manager<br>
> [<a href="http://fsf.org" target="_blank"><a href="http://fsf.org">http://fsf.org</a></a> <a href="http://defectivebydesign.org" target="_blank"><a href="http://defectivebydesign.org">http://defectivebydesign.org</a></a> <a href="http://badvista.fsf.org" target="_blank"><a href="http://badvista.fsf.org">http://badvista.fsf.org</a></a><br>
> <a href="http://playogg.org" target="_blank"><a href="http://playogg.org">http://playogg.org</a></a>]<br>
> Textbook Revolution, editor/(re)designer<br>
> [<a href="http://216.93.249.195/wiki" target="_blank"><a href="http://216.93.249.195/wiki">http://216.93.249.195/wiki</a></a> irc://<a href="http://freenode.net/#textbookrevolution" target="_blank">freenode.net/#textbookrevolution</a>]<br>
> One Laptop per Child, volunteer<br>
> [<a href="http://wiki.laptop.org/go/Participate" target="_blank"><a href="http://wiki.laptop.org/go/Participate">http://wiki.laptop.org/go/Participate</a></a><br>
> irc://<a href="http://freenode.net/#olpc-content" target="_blank">freenode.net/#olpc-content</a>]<br>
> League of Technical Voters, board of directors<br>
> [<a href="http://www.leagueoftechvoters.org/" target="_blank"><a href="http://www.leagueoftechvoters.org/">http://www.leagueoftechvoters.org/</a></a> -<br>
> <a href="http://transparentfederalbudget.com" target="_blank"><a href="http://transparentfederalbudget.com">http://transparentfederalbudget.com</a></a>]<br>
> Free Textbook Project, lead<br>
> [<a href="http://freetextbookproject.org" target="_blank"><a href="http://freetextbookproject.org">http://freetextbookproject.org</a></a> -- more to come]<br>
</div></div><div>> _______________________________________________<br>
> Discuss mailing list<br>
> <a href="mailto:Discuss@lists.flossmanuals.net" target="_blank"><a href="mailto:Discuss@lists.flossmanuals.net">Discuss@lists.flossmanuals.net</a></a><br>
> <a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" target="_blank"><a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a></a><br>
</div>--<br>
<div><div></div><div>Adam Hyde<br>
FLOSS Manuals<br>
<br>
<a href="http://www.flossmanuals.net" target="_blank"><a href="http://www.flossmanuals.net">http://www.flossmanuals.net</a></a><br>
+ 31 6 2808 7108<br>
</div></div><br>_______________________________________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.flossmanuals.net" target="_blank"><a href="mailto:Discuss@lists.flossmanuals.net">Discuss@lists.flossmanuals.net</a></a><br>
<a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" target="_blank"><a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a></a><br>
<br></blockquote></div><br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Discuss mailing list</span><br><span><a href="mailto:Discuss@lists.flossmanuals.net">Discuss@lists.flossmanuals.net</a></span><br><span><a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a></span><br></div></blockquote></body></html>