Help talk:Style/Formatting and punctuation

From ArchWiki
< Help talk:Style
Revision as of 11:27, 8 September 2013 by Kynikos (talk | contribs) (Experimentation session: rm closed)
Jump to: navigation, search

References to titles, headings...

Would you consider the monospaced text at the top of [1] already covered by Help:Style/Formatting_and_Punctuation#Monospace or do we need an additional rule? Personally I would use quote marks in that case, generalizing it as a reference to a title in the article, hence kind of a quotation... -- Kynikos (talk) 10:54, 2 September 2013 (UTC)

I don't see any justification to use monospace according to Help:Style/Formatting_and_Punctuation#Monospace. Also given that the quoted text is not monospaced in the table, it looks weird - so +1 for quote marks. -- Lahwaacz (talk) 11:09, 2 September 2013 (UTC)
Agreed, no reason to use monospace here. The point of monospaced fonts in articles is to convey a meaning separate from that of ordinary English. But those words just have ordinary english meanings, and this is confusing for the reader—it took me longer than usual to understand the point of those sentences, because I was tring to figure out where all those strange "commands" were coming from. Quotation marks are best, but even bold is a more reasonable option than monospace here: the headers themselves are bold, so referencing them in bold makes it immediately clear what we are referring to.
For interesting reading on the subject, the University of Chicago Press suggests:
> If column numbers are mentioned in text, table columns should be numbered accordingly. Numbering should begin with the first column to the right of the stub column.
Which may perhaps be inappropriate for wiki format, but regardless it supports my argument that there are better solutions than monospace font for this problem. The American Psychological Association (APA) Style Guide is more strict, recommending:
> Integrity and Independence. Each table and figure must be intelligible without reference to the text, so be sure to include an explanation of every abbreviation (except the standard statistical symbols and abbreviations).
This has interesting implicaitons. What if we could rewrite this table so that its meaning is immediately obvious? Would that not be better than having a strange explanation in monospaced font at the top of the table, attempting to convince the reader what "dm-crypt +/- LUKS" could possibly mean in this context? -- Ndt (talk) 12:51, 2 September 2013 (UTC)
Thanks for replying, I've added the rule then.
About your idea to rewrite the table, it may even be a good one, but how would you implement that? Personally I don't mind that introduction too much, it doesn't feel "strange" to me. Anyway, I'm closing this discussion, if you want to go further with this proposal, please use Talk:Disk Encryption :)
-- Kynikos (talk) 11:16, 8 September 2013 (UTC)

IP and link-level (MAC) addresses

How do we format IP addresses in text? Use monospace (like in note at the end of Network_Configuration#Check_the_connection) or without formatting (like in Network_Configuration#Static_IP_address)? I think it could be understood as configuration parameter. In any case, it should be stated explicitly, either in Help:Style/Formatting_and_Punctuation#Cases_by_formatting.2Fpunctuation or as an example in Help:Style/Formatting_and_Punctuation#Specific_cases. Link-level addresses should be formatted in the same way (examples: MAC Address Spoofing, QEMU#Link-level address caveat). -- Lahwaacz (talk) 11:00, 3 September 2013 (UTC)

Thanks for mentioning this. Let's keep it simple and coherent and use monospace. Examples are added, closing. -- Kynikos (talk) 11:24, 8 September 2013 (UTC)