Timeline for Pictures of text, acceptable or not?
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:14 | history | edited | CommunityBot |
replaced http://serverfault.com/ with https://serverfault.com/
|
|
| Aug 11, 2014 at 5:05 | comment | added | user9517 | serverfault.com/questions/619443/… | |
| Jul 29, 2014 at 20:01 | comment | added | Rob Moir | Screenshots are not searchable. If the question is otherwise sound (e.g. it's not just "HALP!!!!!11!!!1!one!!one!!1" and a screenshot) then that's an argument in favour of a bit of editing to improve the question rather than closing the question imo. | |
| Jul 28, 2014 at 18:16 | comment | added | voretaq7 Mod | @ewwhite and I'm not inclined to spend time looking for one right now, but I can tell you that I have personally seen and closed several "problem questions" (literally "screenshot of a terminal window"). I don't have a blanket objection to screenshots, but I consider transcribing the relevant portion of their content (like error messages) to be the bare minimum standard of effort. | |
| Jul 28, 2014 at 18:05 | comment | added | ewwhite | @voretaq7 Nobody here has posted an example of a problem question... | |
| Jul 28, 2014 at 18:04 | comment | added | voretaq7 Mod | @ewwhite Non-Searchable things kind of defeat the purpose of Stack Exchange: We're supposed to be building a knowledge base other people can use, and if that knowledge base is obfuscated from search engines its value is greatly diminished. There are some cases where screenshots are the appropriate way to include information, but they're misused far more often by lazy and/or stupid help vampires. | |
| Jul 28, 2014 at 17:57 | comment | added | ewwhite | @voretaq7 They don't have to be. | |
| Jul 28, 2014 at 17:57 | comment | added | voretaq7 Mod | Screenshots are not searchable. | |
| Jul 28, 2014 at 11:48 | history | edited | ewwhite | CC BY-SA 3.0 |
added 927 characters in body
|
| Jul 28, 2014 at 9:56 | comment | added | Rob Moir | I don't see pictures as a problem by default. There are cases where one is preferable to the other of course; for Ed's case here I prefer the picture. If, however, someone screen-shotted windows error message popups then yes, I'd prefer the text. I personally wouldn't see it as an issue that drove me to vote a question up or down or to VTC by itself. | |
| Jul 28, 2014 at 6:24 | comment | added | Håkan Lindqvist | And by "useful to work with" I mean such things as being able to copy part of the text, be it for a quote in an answer, for researching the problem or something else. | |
| Jul 28, 2014 at 6:17 | comment | added | Håkan Lindqvist | My question was focusing on utility rather than aesthetics. The example comes across as an edge case where maybe it subjectively doesn't "look better" (not sure that I think there's really a huge advantage one way or the other, aesthetically) but I would still say that the text version is both more legible and more useful for someone to work with. | |
| Jul 28, 2014 at 6:14 | comment | added | kasperd | On the computer where I am viewing this now, the text version is more readable. Also, posting an image rather than text, can result in duplicate questions being posted. meta.serverfault.com/questions/6334/how-to-deal-with-incorrect-reviews | |
| Jul 28, 2014 at 1:47 | history | answered | ewwhite | CC BY-SA 3.0 |