As far as other languages we have extended discussions about it already in meta, the key points are:
We use English to communicate in the site, both Questions or Answers should be written using a certain level of English, enough to be understood;
Questions made in other languages do not belong in the site, if by any chance a poor soul with some language ...
Answers should always explain. If they don't, they are bad answers even if correct. That said, in most cases, the magical source is simply man command which will print the manual of the command in question. Personally, I try to explain, for example, why I used a particular option for a program by writing something like
As explained in man grep:
This is HTML that works also in the used Markup language here on StackExchange. You would write <kbd>F1</kbd> to achieve F1 (when it is surrounded by ` for code formatting, HTML is ignored). kbd is the abbreviation for keyboard.
Oh, and in comments you also have no HTML support.
For more information, look there:
Firstly, a comment only saying "make it better" is worse than useless. The comment must spell out what needs to happen to make the post better.
That said, there are situations where iterative help is required. The system already suggests breaking out long comment threads into post-specific chat-rooms. They're linked to from the comments, so even after the ...
Even when keeping in mind What is the difference between apt and apt-get? there is still no logical reason to enforce using apt over apt-get/apt-cache. An extra second or two to type 4-6 extra characters is not a major inconvenience and the vast majority of users are not going to care if they're typing apt versus apt-get so long as it gets the job done of ...
We all know the difference:
What is the difference between apt and apt-get?
Both have their merit as both work for the task they are designed to.
This also means there is no reason why we should force people into one or the other.
It is always appropriate to say
Here is the gist of what I'm saying:
It is almost never appropriate to say:
read this and it'll help you.
We do make exceptions for some of the very bleeding edge stuff - for example, Juju in its early early EARLY days was one of those gray areas where we pointed people to the ...
Downvote and flag their answers away (using a custom flag explaining the situation).
Proper attribution is mandatory per how the user provided content is licensed (and I guess those answers would lack it?).
Leveraging the lack of attribution you should at least get those posts deleted; also a certain number of violations of the rules (in this case in ...
The following (without four spaces):
``sudo update-initramfs -v -u -k `uname -r` ``
generates the desired goal:
sudo update-initramfs -v -u -k `uname -r`
Source: How can the backtick character ` be included in code?
I'm not a lawyer but I would like to think I have an understanding of the basics.
The default status for a piece of work is copyright, all rights reserved. So unless stated, you have no permission to copy it (outside fair use/dealing allowances). This does not require somebody to stick Ⓒ Oli 2012 on a bit of work, nor does it require the author to register ...
I differentiate between "Type these commands to do the task" (which should be copy/paste-able), and "Here is what my answer produces on MY system (YMMV)", where the $ and # are used to show context.
A recent example is my answer to this question
Known bug is a too vague category. The bug trackers handle multiple things, from segmentation fault over ugly layout, from feature requests to incompatibilities many things.
The bug-related questions can be about different things, from solving a singular problem, resulting from such a bug, solving the bug, searching for an alternative product without the ...
This is a great alternative. as it sells the branding for Ubuntu Software Center better, as well as serves as a better Call to Action. I'm all for this as an improvement to the current button. However, I don't think it'll work as a drop-in replacement given the current structure of the markup for the button.
It would be great to add it to the current ...
Besides "link rot", it's just a lot easier to see the summary than go to the link. Now it might be that in this one case your link happens to be the perfect help page, but most often, one needs to peruse the webpage and glean what one actually needs to answer the question. I don't actually know if one needs to glean with your link, because I didn't visit ...
If you select/highlight the content and click the <$> code icon it'll do one of two things for you:
If it's part of a line but not a full line, it'll wrap it in ` marks. This gives that section a grey background and changes the text to a monospace font, ideal for code samples.
If it's a full line, or multiple lines, it'll prepend each line with four ...
I think that giving credit by linking the answer that you used in creating your answer is the correct way. This could look like
This answer is partly based on [some link].
Note that you linked the user and not the answer that you used in the answer you refer to.
It's probably on the line.
It doesn't suggest why there's a problem or confirm that it's a problem with a specific browser. If you did this, it would be a much better answer... But it's certainly on its way there.
But I'm saying that with context. I know that on a technical level Chrome likes to block things it considers suspicious. "Try another browser" ...
It sounds like you're on a network that's blocking Imgur. That's where all the images are hosted. You can verify that by trying to visit them. That would explain why the pop-up isn't working and why you can't view images.
You could upload the images to another host but Stack Exchange has an arrangement with Imgur to host files permanently. This is so we don'...
There is pretty good formatting help already if you click the question mark icon on the right of the editing tool bar.
It covers most of the editing questions I've ever had, but I'll admit that it took me a while to find it. Perhaps having a label like "Editing help" next to the icon would make it more obvious to people?
I think you are over-looking something when you assume "the built in reporting tools in Ubuntu do a much better job at collecting the information that developers will need to fix a bug and this is a Question and Answer site, not a bug tracker."
Sometimes the answer to the question is to help a person figure out how to file a bug report. In other words, the ...
I agree that bugs do not belong on Ask Ubuntu, even if Launchpad is not friendly to non-technical users for reporting bugs. The Ubuntu Forums should be the backup option for diagnosing bugs not a Q&A site.
However while I think individual questions should be closed, I think that the best response to these questions as a whole should be trying to create ...
If you think it's completely wrong, the first step should be to point out where the answerer went awry. Leave a comment. This is necessary (in my mind) because you might be wrong and might be misunderstanding the significance of the answer. If you leave a comment, the problem can be addressed, or countered and you can be notified.
Then vote accordingly. If ...
I think in general life, every good answer should be accompanied by at least an impression of it's foundation.
If I give an answer on Askubuntu, I try to make clear if it is based (mostly) on an external source (I add the source as a link), if I speak purely from my own experience, or a combination of both. This gives the user an idea where to find ...
I just noticed, what you are proposing is the same as the question page we have already. Of all the sections you list for the page, only three could be mandatory for every question and they are
Title stating a brief problem description
A description of the problem, and how it is affecting the user
All the others require you to know or provide ...
You lost me at "Hypothetical Situation".
This site is more about solving practical problems that people face regularly every day, not satisfying intellectual curiosity on syncing algorithms. (Though that is an interesting question, I just don't think it's AU material.)
You're missing something. The site uses Markdown formatting and # means h1 in markdown.
You either need to wrap with a pre tag, or use the Markdown code formatting (select the code and press the code icon, or press Control+K).
Using the Markdown is preferred but there are legitimate reasons to use HTML (eg you want to emphasise a line of code). Markdown is ...
How is the noob supposed to know to follow the link to the bug report and elevate the status, as in click "this affects me to"? Or to use the tools available? Judging from the recent graphics and speed issues in Precise, there are bugs that (probably) affect many people but are still tagged as only affecting "1 user" in launchpad.