i really wish i could engage or even post drafts of extensible syntax stuff that i had replied to many years ago and recently.
On 9/29/22, Ihor Radchenko <yanta...@gmail.com> wrote: > Dear List, > > I am forwarding an official email from RMS changing subject line to more > descriptive. See below. > > For some context, in order to support specialized syntax for manuals, we > may first need to implement the discussed special blocks export and > inline special blocks: > 1. https://list.orgmode.org/orgmode/87y1yr9gbl....@gmail.com/ > 2. https://list.orgmode.org/orgmode/87edzqv4ha.fsf@localhost/ > > The above links aim to introduce export functionality that we now have > for links to special blocks and new custom markup elements. I am > referring to > 1. Ability to create new custom element types programmatically > 2. Ability to define how to :export the custom element types > > Similar to `org-link-set-parameters'. > > Patches and more concrete ideas are welcome! > > -------------------- Start of forwarded message -------------------- > From: Richard Stallman <r...@gnu.org> > To: Tim Cross <theophil...@gmail.com> > Cc: emacs-de...@gnu.org > Subject: Re: Org mode and Emacs > Date: Mon, 26 Sep 2022 08:10:03 -0400 > > [[[ 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. ]]] > > Speaking as the Chief GNUisance, rssponsible for GNU Project > standards, I would be happy to adopt an upgraded Org format as a new > standard source format for GNU manuals, _provided_ Org format has been > extended with the capability to express all the constructions and > distinctions that Texinfo can express, generate all the output formats > Texinfo can generate, and use TeX to make beautiful printed output. > > Texinfo can generate these output formats: Info files, HTML, ASCII > text, and DVI and PDF files via TeX. > > Texinfo provides numerous subtle distinctions that show up clearly in > each of these output formats. Compare, for example, @var, @dfn and > @emph; compare @code, @samp, @file, @command, @option, @kbd, and @key. > > I am sure people can extend Org software to handle these semantic > distinctions and generate these output formats. Since it has been > done once, it can be done again. But the work is not trivial. > > The work has to start by designing what the extended Org format will look > like. That part is the crucial part; once it has been specified, > people can work independently to implement various parts of handling > that format. > > -- > Dr Richard Stallman (https://stallman.org) > Chief GNUisance of the GNU Project (https://gnu.org) > Founder, Free Software Foundation (https://fsf.org) > Internet Hall-of-Famer (https://internethalloffame.org) > > > > -------------------- End of forwarded message -------------------- > > -- > Ihor Radchenko, > Org mode contributor, > Learn more about Org mode at https://orgmode.org/. > Support Org development at https://liberapay.com/org-mode, > or support my work at https://liberapay.com/yantar92 > > -- The Kafka Pandemic A blog about science, health, human rights, and misopathy: https://thekafkapandemic.blogspot.com
