View Single Post
Old 08-14-2011, 09:36 PM   #1
Halo
Connoisseur
Halo did not drink the Kool Aid.Halo did not drink the Kool Aid.Halo did not drink the Kool Aid.Halo did not drink the Kool Aid.Halo did not drink the Kool Aid.Halo did not drink the Kool Aid.Halo did not drink the Kool Aid.Halo did not drink the Kool Aid.Halo did not drink the Kool Aid.Halo did not drink the Kool Aid.Halo did not drink the Kool Aid.
 
Halo's Avatar
 
Posts: 96
Karma: 72130
Join Date: Nov 2008
Location: San Francisco Bay Area, CA, USA
Device: Sony PRS-505, Kindle DX 1st Gen, Kindle Fire 1st Gen
Formatting for documentation source code

There doesn't seem to be any standard to how the source code for the documentation is formatted. Some lines wrap at one length while others are at longer lengths. Some have whole paragraphs on a single line.

Would there be any objection if I were to wrap lines at 78 characters as I make edits to the documentation? I would only change the lines or paragraphs that I edit for content. Alternatively, if there is consensus on a standard, I would be happy to reformat all of the doc source and submit it in a single commit.

I would also like to include some "vim hints" at the beginning or end of each doc source file to help enforce editor setting consistency, provided no one objects.
Halo is offline   Reply With Quote