On 3/2/06, <b class="gmail_sendername">Patrick R. Michaud</b> <<a href="mailto:pmichaud@pobox.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">pmichaud@pobox.com</a>> wrote:<div><span class="gmail_quote">
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Do we need to have both the TextFormattingRules and BasicEditing<br>pages? They seem largely duplicative. If we need both, what's<br>the main difference between them?<br></blockquote></div><br>Assuming that no minor markups have slipped through the cracks, the difference is in the approach. Text Formatting Rules is for people like me, who like to read the manual and understand how the thing works. Basic Editing is much more a "get the job done" page.
<br><br>In either case, what I care about is that <br>* all the text formatting markups are covered<br>* there's enough information and examples that I can understand how the markups work (Text Formatting Rules is generally better at this, for me)
<br>
* I know where to go for more information on certain things, like links or directives<br>* I can quickly find the markup I'm looking for, either by seeing the effect, or by the name.<br><br>Basic Editing makes it easier to find something by how it looks, but harder to find it by name. Honestly, somewhere back in the betas for
2.0 I wrote my own Text Formatting Rules, and have been using it happily since, because its organization makes sense to me. It complements my custom edit quickref nicely -- the quickref is a markup -> effect table -- and most of the stuff that's changed since has been directives and other things that never lived in TFR anyway. There's section headings in the quickref that take you to the proper anchor in the TRF when you need to learn more.
<br><br>Bronwyn