Is there a rule against which
markdown codes are allowed in formatting text for easy reading? It's my impressing that a lot of text that is displayed that isn't code is displayed using code tags to control the way it's output.
Is it alright for me to say, I have these four items,
apples, oranges, peaches, and pears to choose from. When it's a list of items that I hope to stand out rather than code that someone will execute?
I have studied a lot of details of
markdown and am still studying how to make my messages easy to read. I'm learning new things every day. I even go back and edit many of my previous messages as I learn.
But looking at a recent edit and not on the edit purpose, it appears to be suggesting that I can't use the
backtick for formatting when it's not code.
Losing this as an option, will make my messages even harder for me to review when checking for adequacy.
I'm asking question for input because of a recent edit of one of this answer:
Please don't use code formatting for emphasis
First I really appreciate people taking the time to help make my answers (as well as all all the other answers on SE) easy to read. But some of the changes as in the case of revision #4 of that particular message, makes
my reading it substantially more time consuming and requiring more effort.
I can tell that many of our users go far in trying to make their messages easy to read. They add pictures, when sometimes I think the text would be easier.
I often try to put lots of white spaces in my messages, when some people try not to use white spaces and put what I consider too much into one paragraph.
Thanks in advance for comments from others on permission for using the
code formatting markdown feature for readability.
Update with examples:
My original question was concerning the rules on emphasis. I appreciate the response to perspective of my question. However, most of the focus was "understandably" about emphasis. I used the word emphasis because of the note that was attached to the answer I linked in my question.
However, I was not using the
backticks as for emphasis. I was using it the way the examples in the photos below.
To me there is a difference, and I agree with the consensus about the emphasis. To me (and concerning my writing and speaking style), emphasizing something is to stress it. Defining and separating something as in, keywords, is different. I understand that my keyword specification may not have been clear to the some. But that was the reason for the way I used the formatting, to specify my intentions with the words. It wasn't my intentions for the words to stand out and be spoken louder. It was my intention for the keywords to be read as in a special definitive manner.
My intentions with the formating was to format the way you see the formating in the images below. The red arrows are pointing to targets items that are specified in the manner of my intentions. They are not specified to be emphasized or yelled out.
code formattingfor emphasis can be confusing, because most users expect those to be code or code-like elements.
share edit close delete flaglooks the same way the text that I separate in my message. It's not confusing. It's showing me the text is set apart and different from the text above it. That was my intentions in my message.
htmlto help in my formatting, but haven't found something that presents intent in the cases where I used the backticks as well as they display.
*...*in markdown, respectively).
backticksin my questions are not emphases... to stress words, or say them louder. It's about separating the words with some type of definition. It would make more sense to say look at your
/home/Documentsfolder than to say look at your /home/Documets folder. The later is placing emphases on the folder, whereas my intentions isn't to emphasize the folder, but to set it apart, as something being defined in the message, or having a special definition. Reading aloud the a message, /home/Documents text would be toned different from reading