Re: Convert README.org to plain text README while installing package

[Jean Louis <bugs@gnu.support>]

It was not the point if file is readable by computer program named text editor.

The point is if it is readable for human.

There are many Emacs users who don't use Org. They are not supposed to decipher brackets, properties, links, and lack of authors' sense in writing Org files in human readable manner.

This whole subject is related to accessibility, Org files could be accessible and thus well readable if they would be just simple text without any markup, without  headings, but they are practically not so. Authors write headings without space to its paragraph, it destroys the original meaning of the heading, file does not convey the intended idea unless you are Emscd wizard.

Difficulties in reading reject users.

I will give you examples later.

On June 8, 2022 6:50:24 AM UTC, Tim Cross <theophilusx@gmail.com> wrote:
>
>Jean Louis <bugs@gnu.support> writes:
>
>> * Tim Cross <theophilusx@gmail.com> [2022-06-06 15:57]:
>>> Org files *are* plain text. This is one of (perhaps the biggest)
>selling
>>> points for org mode.
>>
>> We may call it "plain text" and problem is not that we can open Org
>> files with any editor as plain text, but in formatting. People format
>> Org files in such ways that they are not readable, they may not make
>> spacing where it would be otherwise required, in other words, plain
>> text files do not look nearly as readable as for example RFC text,
>> like this one: https://www.rfc-editor.org/rfc/rfc1.txt
>
>Please give me an example of org mode 'not make space where it would be
>otherwise required'. Can you provide a single example of org mode
>syntax which is not readable in any text editor. There are quite a few
>projects on Github/Gitlab which have readme.org files - can you point
>to
>one which cannot be read with a plain text editor? 


Jean