From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Porter Subject: Re: bug#32722: 26.1; Org-publish depend on non-free platform ? Date: Thu, 20 Sep 2018 00:21:33 -0500 Message-ID: <87bm8sg2w2.fsf@alphapapa.net> References: <531a7f93882cc0d5d09700457d06ea082f47569b.camel@flqt.fr> <83sh2ck42e.fsf@gnu.org> <87va73gn90.fsf@nicolasgoaziou.fr> <83efdqg32d.fsf@gnu.org> <87lg7yfraw.fsf@nicolasgoaziou.fr> <831s9qezqo.fsf__19979.8045600348$1537340533$gmane$org@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50843) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g2rPZ-0007U6-Oa for emacs-orgmode@gnu.org; Thu, 20 Sep 2018 01:21:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g2rPV-0000GD-NR for emacs-orgmode@gnu.org; Thu, 20 Sep 2018 01:21:57 -0400 Received: from [195.159.176.226] (port=47494 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1g2rPR-00008p-VL for emacs-orgmode@gnu.org; Thu, 20 Sep 2018 01:21:51 -0400 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1g2rNC-00064T-Nr for emacs-orgmode@gnu.org; Thu, 20 Sep 2018 07:19:30 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Although I've read all of the messages in it, this thread has not been especially easy to follow. Whatever changes are made, we should ensure that there are no regressions as a result. This should mean that: 1. Existing Org users who install the new version of Org and export documents to HTML should not see any changes in the output. 2. New Org users whose first version is the new one should be able to easily get the same HTML output they see existing users getting. If the changes in documentation and in-Emacs messages obscure the necessary steps, it should be considered a significant regression in usability. I can already imagine the messages asking, "How do I get the nice-looking, syntax-highlighted code blocks I see all the other Org users getting?" There are already many questions about Org that are asked over and over again in various places. Let's not add a new one to that list, about something that used to work fine.