From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: On being web-friendly and why info must die Date: Sat, 13 Dec 2014 07:46:45 -0500 Message-ID: References: <20141205123549.GA29331@thyrsus.com> <5484FF31.5010808@cs.ucla.edu> <5485FC59.5030700@cs.ucla.edu> <87388p6glt.fsf@engster.org> <871to9lw6g.fsf@fencepost.gnu.org> <5486A704.6090305@cs.ucla.edu> <87k321jj4e.fsf@fencepost.gnu.org> <54876F7F.9000607@cs.ucla.edu> <87y4qfj2u9.fsf@fencepost.gnu.org> <54889A57.5060905@cs.ucla.edu> <87vbljb9f4.fsf@wanadoo.es> <54889F6D.6060408@cs.ucla.edu> <87r3w7b83a.fsf@wanadoo.es> <5488C710.3000209@cs.ucla.edu> <871to7ayv9.fsf@wanadoo.es> <5488DC0C.2070402@cs.ucla.edu> <837fxyt78a.fsf@gnu.org> <87iohiujcy.fsf@Gertrud.fritz.box> <8761dg1ykk.fsf@Gertrud.fritz.box> Reply-To: rms@gnu.org NNTP-Posting-Host: plane.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: ger.gmane.org 1418474826 24033 80.91.229.3 (13 Dec 2014 12:47:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 13 Dec 2014 12:47:06 +0000 (UTC) Cc: emacs-devel@gnu.org To: Achim Gratz Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 13 13:47:01 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Xzm69-0004wI-Ir for ged-emacs-devel@m.gmane.org; Sat, 13 Dec 2014 13:47:01 +0100 Original-Received: from localhost ([::1]:32774 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xzm69-0005rx-7G for ged-emacs-devel@m.gmane.org; Sat, 13 Dec 2014 07:47:01 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56700) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xzm5v-0005rf-IR for emacs-devel@gnu.org; Sat, 13 Dec 2014 07:46:48 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xzm5u-0002Sq-Lf for emacs-devel@gnu.org; Sat, 13 Dec 2014 07:46:47 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:37892) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xzm5u-0002Sm-IV for emacs-devel@gnu.org; Sat, 13 Dec 2014 07:46:46 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1Xzm5t-0001QP-Pf; Sat, 13 Dec 2014 07:46:45 -0500 In-reply-to: <8761dg1ykk.fsf@Gertrud.fritz.box> (message from Achim Gratz on Fri, 12 Dec 2014 20:02:19 +0100) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:179991 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > I've left out the preamble of the manual that defines the title, among > other things. In general I'd thing Org would need to have a derived > export backend for the kind of manuals you are thingkning about that > took care about these things. Documentation of how to write such things in Org format is part of what is needed for Org format to be a candidate for a GNU documentation format. > > Is there a way to distinguish between emphasis and definitional > > occurrences and variable values? In Texinfo, @emph and @dfn and @var. > > They all appear as italic in printed manuals, but may be different > > in other output formats. > See, that's one thing no "unobtrusive" or "visual" markup can provide. I do see that it is not straightforward -- but this feature is something we need. > For Org, it seems that macros would be the way to go unless we'd come up > with yet another mechanism for semantic markup. What would this look like? A solution that occurs to me is to use character pair brackets, such as _*foo*_ and _#foo#_ and *#foo#*. These would provide enough alternatives to make the necessary distinctions. -- Dr Richard Stallman President, Free Software Foundation 51 Franklin St Boston MA 02110 USA www.fsf.org www.gnu.org Skype: No way! That's nonfree (freedom-denying) software. Use Ekiga or an ordinary phone call.