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 09:02:38 +0300 Message-ID: <83r13uwha9.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> <87wndmwrrk.fsf@gmail.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34931"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, monnier@iro.umontreal.ca, acm@muc.de, 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 08:07:46 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 1o0GlG-0008t1-8L for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Jun 2022 08:07:46 +0200 Original-Received: from localhost ([::1]:35402 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o0GlE-0006ZN-Ec for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Jun 2022 02:07:44 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60724) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0Ggj-0004eI-Fc for emacs-devel@gnu.org; Sun, 12 Jun 2022 02:03:08 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:41254) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0Ggg-0007S2-VK; Sun, 12 Jun 2022 02:03:04 -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=abqtSEJ9b2yFEQYYgJhDx+t6GLGUrvhGbN0TnW8xVk8=; b=TNWmbuG9+ZOm 54W0brjZ7y5ma/A8gZyqZslwZ4umpsgYLQ0mo6sMqot5WbmpwQbqoW6JrO4AISH1GsM7Nt6OEFpRU +L8S2eA8wAPiJZkjAuBSQJ5EHuH1A8ZYOxIY1W/CpAHUaa1WwqEYVrpyu9LxpKisotV1CybPCnt5z L+xHVmq0c3RKvxjw/8sAxcjzCHwIqpe8c9O7irwRdgZ3QvhDJiwUe1UWdg+cqV9og3t3N16mM5QrR en4t63ENoevb2qBYzmAiJdGjBlgc0AdMIXp+GvBCFto8/NcoACxsHkS1LgWD3wF6bzYSYvatcQeu1 F9j/bu36MIjIYQEMtUqckg==; Original-Received: from [87.69.77.57] (port=2113 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 1o0GgX-0000fP-Q4; Sun, 12 Jun 2022 02:02:54 -0400 In-Reply-To: <87wndmwrrk.fsf@gmail.com> (message from Tim Cross on Sun, 12 Jun 2022 11:39:07 +1000) 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:291071 Archived-At: > From: Tim Cross > Cc: monnier@iro.umontreal.ca, acm@muc.de, emacs-devel@gnu.org > Date: Sun, 12 Jun 2022 11:39:07 +1000 > > The other side of th coin is the on-going development of texinfo. I have > not written enough texinfo to really understand what the issues are > which drive the desire to replace it with something else, such as org. I > know there are some criticisms regarding output formats, but I also know > there is on-going work to improve that situation. Is the right strategy > to work on org mode so that it can replace texinfo or work on texinfo to > address limitations (or both?)? The main problem with Texinfo that I'm aware of is its reliance on TeX for the printed output formats (PDF, PS, etc.). Many restrictions in Texinfo come from the fact that something is impossible to implement in TeX. Another issue that frequently comes up is the HTML format it produces: it currently doesn't support many features expected from good on-line documentation, such as multiple frames etc. A better place to discuss the shortcomings of Texinfo is on the Texinfo mailing list, where we can talk to the few people who are actively developing Texinfo and aware of the main issues.