Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
There are multiple reasons why using images of code, errors, logs and other text resources used in programming instead of the actual text is strongly discouraged. Shortly put, the question should ...
Answer
#5: Post edited
by
Andreas witnessed the end of the world today
·
2024-09-23T21:00:33Z (about 2 months ago)
Seemed as if the list was going to explain why using text is good, yet it explains why using images is bad.
- There are multiple reasons why using images of code, errors, logs and other text resources used in programming instead of the actual text is _strongly discouraged_.
- Shortly put, the question should be written in a form that **helps both the fellow community members to answer it** (e.g. easy to copy-paste the code to provide an answer) **and the future readers** (e.g. read and copy-paste the code).
Reasons to paste text instead of images:- - **hard to get the text** - it is harder to get the text from an image than a direct copy-paste. This means wasted time for a person who wants to answer it due to extra effort involved in retyping the provided code
- - **harder to read** - most of the images will be shrunk to fit the post maximum width, will be unreadable and thus force the reader to open it separately to view it full width
- - **non-searchability** - site search or search engine will not get to the text inside the image
- - **non-accessibility** - screen readers need to be [way smarter](https://tink.uk/thoughts-on-screen-readers-and-image-recognition) to get the text from an image, so it will make life harder for those with visual impairments
- - **hides formatting, whitespace, or incorrect characters** - prevents the readers from fully understanding some possible errors caused by incorrect indentation, non-visible characters or Unicode characters that look identical to the ANSI ones
- Note: This post was inspired by [a very similar SO one](https://meta.stackoverflow.com/a/285557/2780791).
- There are multiple reasons why using images of code, errors, logs and other text resources used in programming instead of the actual text is _strongly discouraged_.
- Shortly put, the question should be written in a form that **helps both the fellow community members to answer it** (e.g. easy to copy-paste the code to provide an answer) **and the future readers** (e.g. read and copy-paste the code).
- Reasons to avoid images of text:
- - **hard to get the text** - it is harder to get the text from an image than a direct copy-paste. This means wasted time for a person who wants to answer it due to extra effort involved in retyping the provided code
- - **harder to read** - most of the images will be shrunk to fit the post maximum width, will be unreadable and thus force the reader to open it separately to view it full width
- - **non-searchability** - site search or search engine will not get to the text inside the image
- - **non-accessibility** - screen readers need to be [way smarter](https://tink.uk/thoughts-on-screen-readers-and-image-recognition) to get the text from an image, so it will make life harder for those with visual impairments
- - **hides formatting, whitespace, or incorrect characters** - prevents the readers from fully understanding some possible errors caused by incorrect indentation, non-visible characters or Unicode characters that look identical to the ANSI ones
- Note: This post was inspired by [a very similar SO one](https://meta.stackoverflow.com/a/285557/2780791).
#4: Post edited
by
trichoplax
·
2023-02-03T06:36:59Z (almost 2 years ago)
Typos
There are multiple reasons why using images of code, error, logs and other text resources used in programming instead of the actual text is _strongly discouraged_.- Shortly put, the question should be written in a form that **helps both the fellow community members to answer it** (e.g. easy to copy-paste the code to provide an answer) **and the future readers** (e.g. read and copy-paste the code).
- Reasons to paste text instead of images:
- **hard to get the text** - it is harder to get the text from an image than a direct copy-paste. This means wasted time for a person who want to answer it due to extra effort involved in retyping the provided code- - **harder to read** - most of the images will be shrunk to fit the post maximum width, will be unreadable and thus force the reader to open it separately to view it full width
- - **non-searchability** - site search or search engine will not get to the text inside the image
- - **non-accessibility** - screen readers need to be [way smarter](https://tink.uk/thoughts-on-screen-readers-and-image-recognition) to get the text from an image, so it will make life harder for those with visual impairments
- - **hides formatting, whitespace, or incorrect characters** - prevents the readers from fully understanding some possible errors caused by incorrect indentation, non-visible characters or Unicode characters that look identical to the ANSI ones
- Note: This post was inspired by [a very similar SO one](https://meta.stackoverflow.com/a/285557/2780791).
- There are multiple reasons why using images of code, errors, logs and other text resources used in programming instead of the actual text is _strongly discouraged_.
- Shortly put, the question should be written in a form that **helps both the fellow community members to answer it** (e.g. easy to copy-paste the code to provide an answer) **and the future readers** (e.g. read and copy-paste the code).
- Reasons to paste text instead of images:
- - **hard to get the text** - it is harder to get the text from an image than a direct copy-paste. This means wasted time for a person who wants to answer it due to extra effort involved in retyping the provided code
- - **harder to read** - most of the images will be shrunk to fit the post maximum width, will be unreadable and thus force the reader to open it separately to view it full width
- - **non-searchability** - site search or search engine will not get to the text inside the image
- - **non-accessibility** - screen readers need to be [way smarter](https://tink.uk/thoughts-on-screen-readers-and-image-recognition) to get the text from an image, so it will make life harder for those with visual impairments
- - **hides formatting, whitespace, or incorrect characters** - prevents the readers from fully understanding some possible errors caused by incorrect indentation, non-visible characters or Unicode characters that look identical to the ANSI ones
- Note: This post was inspired by [a very similar SO one](https://meta.stackoverflow.com/a/285557/2780791).
#3: Post edited
by
ghost-in-the-zsh
·
2023-01-28T09:01:12Z (almost 2 years ago)
Word change for readability
There are multiple reasons why using images of code, error, logs and other text resources used in programming instead of the actual text is _strongly not recommended_.- Shortly put, the question should be written in a form that **helps both the fellow community members to answer it** (e.g. easy to copy-paste the code to provide an answer) **and the future readers** (e.g. read and copy-paste the code).
- Reasons to paste text instead of images:
- - **hard to get the text** - it is harder to get the text from an image than a direct copy-paste. This means wasted time for a person who want to answer it due to extra effort involved in retyping the provided code
- - **harder to read** - most of the images will be shrunk to fit the post maximum width, will be unreadable and thus force the reader to open it separately to view it full width
- - **non-searchability** - site search or search engine will not get to the text inside the image
- - **non-accessibility** - screen readers need to be [way smarter](https://tink.uk/thoughts-on-screen-readers-and-image-recognition) to get the text from an image, so it will make life harder for those with visual impairments
- - **hides formatting, whitespace, or incorrect characters** - prevents the readers from fully understanding some possible errors caused by incorrect indentation, non-visible characters or Unicode characters that look identical to the ANSI ones
- Note: This post was inspired by [a very similar SO one](https://meta.stackoverflow.com/a/285557/2780791).
- There are multiple reasons why using images of code, error, logs and other text resources used in programming instead of the actual text is _strongly discouraged_.
- Shortly put, the question should be written in a form that **helps both the fellow community members to answer it** (e.g. easy to copy-paste the code to provide an answer) **and the future readers** (e.g. read and copy-paste the code).
- Reasons to paste text instead of images:
- - **hard to get the text** - it is harder to get the text from an image than a direct copy-paste. This means wasted time for a person who want to answer it due to extra effort involved in retyping the provided code
- - **harder to read** - most of the images will be shrunk to fit the post maximum width, will be unreadable and thus force the reader to open it separately to view it full width
- - **non-searchability** - site search or search engine will not get to the text inside the image
- - **non-accessibility** - screen readers need to be [way smarter](https://tink.uk/thoughts-on-screen-readers-and-image-recognition) to get the text from an image, so it will make life harder for those with visual impairments
- - **hides formatting, whitespace, or incorrect characters** - prevents the readers from fully understanding some possible errors caused by incorrect indentation, non-visible characters or Unicode characters that look identical to the ANSI ones
- Note: This post was inspired by [a very similar SO one](https://meta.stackoverflow.com/a/285557/2780791).
#2: Post edited
by
Alexei
·
2021-11-13T17:22:51Z (about 3 years ago)
added SO source
- There are multiple reasons why using images of code, error, logs and other text resources used in programming instead of the actual text is _strongly not recommended_.
- Shortly put, the question should be written in a form that **helps both the fellow community members to answer it** (e.g. easy to copy-paste the code to provide an answer) **and the future readers** (e.g. read and copy-paste the code).
- Reasons to paste text instead of images:
- - **hard to get the text** - it is harder to get the text from an image than a direct copy-paste. This means wasted time for a person who want to answer it due to extra effort involved in retyping the provided code
- - **harder to read** - most of the images will be shrunk to fit the post maximum width, will be unreadable and thus force the reader to open it separately to view it full width
- - **non-searchability** - site search or search engine will not get to the text inside the image
- - **non-accessibility** - screen readers need to be [way smarter](https://tink.uk/thoughts-on-screen-readers-and-image-recognition) to get the text from an image, so it will make life harder for those with visual impairments
- - **hides formatting, whitespace, or incorrect characters** - prevents the readers from fully understanding some possible errors caused by incorrect indentation, non-visible characters or Unicode characters that look identical to the ANSI ones
- There are multiple reasons why using images of code, error, logs and other text resources used in programming instead of the actual text is _strongly not recommended_.
- Shortly put, the question should be written in a form that **helps both the fellow community members to answer it** (e.g. easy to copy-paste the code to provide an answer) **and the future readers** (e.g. read and copy-paste the code).
- Reasons to paste text instead of images:
- - **hard to get the text** - it is harder to get the text from an image than a direct copy-paste. This means wasted time for a person who want to answer it due to extra effort involved in retyping the provided code
- - **harder to read** - most of the images will be shrunk to fit the post maximum width, will be unreadable and thus force the reader to open it separately to view it full width
- - **non-searchability** - site search or search engine will not get to the text inside the image
- - **non-accessibility** - screen readers need to be [way smarter](https://tink.uk/thoughts-on-screen-readers-and-image-recognition) to get the text from an image, so it will make life harder for those with visual impairments
- - **hides formatting, whitespace, or incorrect characters** - prevents the readers from fully understanding some possible errors caused by incorrect indentation, non-visible characters or Unicode characters that look identical to the ANSI ones
- Note: This post was inspired by [a very similar SO one](https://meta.stackoverflow.com/a/285557/2780791).
#1: Initial revision
by
Alexei
·
2021-11-13T17:21:50Z (about 3 years ago)
There are multiple reasons why using images of code, error, logs and other text resources used in programming instead of the actual text is _strongly not recommended_. Shortly put, the question should be written in a form that **helps both the fellow community members to answer it** (e.g. easy to copy-paste the code to provide an answer) **and the future readers** (e.g. read and copy-paste the code). Reasons to paste text instead of images: - **hard to get the text** - it is harder to get the text from an image than a direct copy-paste. This means wasted time for a person who want to answer it due to extra effort involved in retyping the provided code - **harder to read** - most of the images will be shrunk to fit the post maximum width, will be unreadable and thus force the reader to open it separately to view it full width - **non-searchability** - site search or search engine will not get to the text inside the image - **non-accessibility** - screen readers need to be [way smarter](https://tink.uk/thoughts-on-screen-readers-and-image-recognition) to get the text from an image, so it will make life harder for those with visual impairments - **hides formatting, whitespace, or incorrect characters** - prevents the readers from fully understanding some possible errors caused by incorrect indentation, non-visible characters or Unicode characters that look identical to the ANSI ones