From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.devel Subject: Re: Convert README.org to plain text README while installing package Date: Sun, 12 Jun 2022 14:41:19 +0300 Message-ID: References: <87h74ztshe.fsf@gmx.de> <871qw31ois.fsf@yahoo.com> <8735gj4ceo.fsf@gnu.org> <87ee038ipt.fsf@gmx.de> <87o7z61v59.fsf@gmail.com> <87ilpbzlq5.fsf@gmail.com> <87sfoawp1u.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27829"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/+ () (2022-05-21) Cc: emacs-devel@gnu.org To: Tim Cross Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jun 12 18:54:08 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o0Qql-00073L-Tt for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Jun 2022 18:54:07 +0200 Original-Received: from localhost ([::1]:54212 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o0Qqk-0000yi-Cg for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Jun 2022 12:54:06 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36970) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0QpM-0007v2-IW for emacs-devel@gnu.org; Sun, 12 Jun 2022 12:52:40 -0400 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:36585) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0QpK-0003i8-Tc for emacs-devel@gnu.org; Sun, 12 Jun 2022 12:52:40 -0400 Original-Received: from localhost ([::ffff:102.84.37.119]) (AUTH: PLAIN admin, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 0000000000087C59.0000000062A619B5.0000608B; Sun, 12 Jun 2022 09:52:05 -0700 Mail-Followup-To: Tim Cross , emacs-devel@gnu.org Content-Disposition: inline In-Reply-To: <87sfoawp1u.fsf@gmail.com> Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -2 X-Spam_score: -0.3 X-Spam_bar: / X-Spam_report: (-0.3 / 5.0 requ) BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:291099 Archived-At: * Tim Cross [2022-06-12 06:15]: > I gues sour differences here are that you have conflated issues of > readabiity and usability into the definition of plain text. I did not. I speak of understanding of package descriptions. When user clicks on a package within Emacs that user expects package description, not a markup. It is totally irrelevant for user if markup and tags, properties are plain text in the context of editors. What matters is if user is helped to understand the package description. Or maybe user is obstructed to understand it. > Few of the criticisms you have raised IMO are specific to org mode > or due to org modes syntax. They are not specific, it just happens that I had in my package list several Org type package descriptions. If too complex Markdown markup is used it will also obstruct user to understand package description. > Many of them are due to the individual author's layout and not the > result of org mode syntax. You can also write documents which are > very difficult to read using just plain ASCII. They are both plain > text. I do not think that "plain text" is relevant. HTML markup is also plain text, it is irrelevant in the context of a user reading package descriptions. User is not supposed to read HTML tags either, right? > I also think you are over-stating the difficulty of reading the raw org > file contents. While I would agree they are asier to read when correctly > formatted, they are not impossible to understand without it. You may stay in your viewpoint of knowledgable Emacs user, in that sense there is also no need for package descriptions, then we can simply tell users to read sources (irony). One has to mentally become a user who does not know Org, the one who simply wants to find out what package is about. Only so one can understand it. -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/