/|\

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
talk:slackdocs:styleguide [2012/09/04 05:15 (UTC)]
kikinovak
talk:slackdocs:styleguide [2012/09/08 14:03 (UTC)]
alienbob
Line 18: Line 18:
  
 ---- ----
-Shouldn't the Style Guide also be signed by its author? [[wiki:user:kikinovak|Niki Kovacs]] Tue Sep  4 07:14:48 CEST 2012//+Shouldn't the Style Guide also be signed by its author? [[wiki:user:kikinovak|Niki Kovacs]] Tue Sep  4 07:14:48 CEST 2012 
 + 
 +>Most Slackdocs documentation, if not all, has been written by staff. Personally, I don't care about author attribution on these "rules and regs" type articles. Many of the articles, this one for instance, have numerous contributors. Just my thoughts. :-)  --- //[[wiki:user:nocturnal.slacker|V. T. Eric Layton]] 2012/09/04 10:45// 
 ---- ----
 +"Follow proper capitalization rules for words in titles and headings." Aren't we being pedantic? Personally, I find this a little too fussy and unnecessary. A Pain In The Arse, or a Pain in the Arse.  --- //[[wiki:user:brianl|Brian Lawrence]] 2012/09/08 06:01//
 +----
 +I had the same thought about that. Capitalizing every word is typical US-english style. We are trying to not just cater to the US population, remember? I personally think capitalizing every word is ugly. Try capitalizing a whole sentence... it looks awful. \\ Nevertheless, from the point of view of "unified look and feel" I can understand why you would want all headers capitalized. \\  --- //[[wiki:user:alienbob|Eric Hameleers]] 2012/09/08 06:59//
 +
 +
  

In Other Languages
QR Code
QR Code talk:slackdocs:styleguide (generated for current page)