From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Org mode and Emacs (was: Convert README.org to plain text README while installing package) Date: Sun, 12 Jun 2022 08:45:32 +0300 Message-ID: <83v8t6wi2r.fsf@gnu.org> References: <87h74ztshe.fsf@gmx.de> <871qw31ois.fsf@yahoo.com> <8735gj4ceo.fsf@gnu.org> <87ee038ipt.fsf@gmx.de> <87o7z61v59.fsf@gmail.com> <87bkv527p5.fsf@gmail.com> <835yld93w7.fsf@gnu.org> <877d5t0yrn.fsf@gmail.com> <87r140yuof.fsf@gmail.com> <875yl9e7zm.fsf@gmail.com> <83czfh12kp.fsf@gnu.org> <87pmjhghu2.fsf@localhost> <835yl910gp.fsf@gnu.org> <87wndndbhq.fsf@gmail.com> <874k0qbrhe.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27489"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, theophilusx@gmail.com, monnier@iro.umontreal.ca, acm@muc.de, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jun 12 07:48:54 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 1o0GT0-0006zX-1r for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Jun 2022 07:48:54 +0200 Original-Received: from localhost ([::1]:55692 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o0GSy-0007Gf-L7 for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Jun 2022 01:48:52 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59308) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0GQN-0006OX-Nf for emacs-devel@gnu.org; Sun, 12 Jun 2022 01:46:13 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:41074) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0GQM-0005Tr-TI; Sun, 12 Jun 2022 01:46:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=49lEuImna04TB5OPZtHuOym0tDd+vmuzwvD07Jabh94=; b=jsPGoDs6TZvp Q9uErQUrUOg+JXsElXItGgFMYaI2ZiMNpGHf0ov/8xl7eSqwd8OP9LQjdwbRKjCZ94M4o3rm28/8K N20HaiN8/CjM2CHsjvgNmAW/05rDZ+kY3UgLE0xCPfhE2HslB9qmiNpKLXHH5ZkZ3Q352Cnjk5pyK kF5X67H+wPr8wAnSv4KzUDyqPVRfLD3aURh1QD5t7OJ39+HS1cM3wASwXfCc4eYFLSQ+K6QiZPY12 OdYlrdnXOfxe07rrTk9Zn/W35EvypanMEUSIMkfOenFfEt/5eI0kzS3C/bcmNJKrlH9h7sDvsx/N1 r49tcLMNT5ukapkEZPXdIw==; Original-Received: from [87.69.77.57] (port=1063 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0GQ1-0004Cs-Il; Sun, 12 Jun 2022 01:45:50 -0400 In-Reply-To: <874k0qbrhe.fsf@localhost> (message from Ihor Radchenko on Sun, 12 Jun 2022 09:27:57 +0800) 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:291069 Archived-At: > From: Ihor Radchenko > Cc: Tim Cross , eliz@gnu.org, > monnier@iro.umontreal.ca, acm@muc.de, emacs-devel@gnu.org > Date: Sun, 12 Jun 2022 09:27:57 +0800 > > Richard Stallman writes: > > > One of Texinfo's crucial features is a wide range of semantic markup > > constructs, each of which can generate different output depending on > > the output format. For instance, Texinfo has @var, @emph and @dfn, > > all of which generate italics in printed output, but they differ in > > what they generate for other output formats. There are probably 15 > > other such constructs. > > Could you please point to the place where I can read about the different > generated output? In the Texinfo manual. It describes, for each markup, what that produces in every major output format. > > Does Org format have the ability to make all these distinctions? > > If not, I suspect that the Org mode documentation isn't following > > all our style conventions for documentation. > > Org manual does not AFAIK, other than various index entries. That is strange to hear. I was under the impression that Org can export to various format, and each such output format has its own export support. So at least in principle, the distinction Richard is talking about should be not only possible, but quite easy to implement, if not already implemented. > However, I am not sure what exactly you are referring to. > Could you please provide a link describing the conventions you are > referring to? Most of them are in the Texinfo manual, and some are in the GNU Coding Standards manual. To take one example, @dfn produces italics in HTML and in printed formats (PDF etc.), and quoted text in Info.