From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/10231 Path: news.gmane.org!not-for-mail From: Jonathan Clark Newsgroups: gmane.text.pandoc Subject: Re: Footnotes plus endnotes in Markdown Date: Tue, 1 Jul 2014 03:53:19 -0700 (PDT) Message-ID: <1546019c-186f-4a9c-ad6c-7166567c1b8d@googlegroups.com> References: <973d1e4c-f49b-4c81-a69f-8a393954f237@googlegroups.com> <87d2dqo6qu.fsf@jhu.edu> <871tu6rto6.fsf@jhu.edu> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1332_4535905.1404211999507" X-Trace: ger.gmane.org 1404212007 16666 80.91.229.3 (1 Jul 2014 10:53:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 1 Jul 2014 10:53:27 +0000 (UTC) Cc: andunning-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-X-From: pandoc-discuss+bncBDYKRK5OU4DRBIFGZKOQKGQEOYWIC4A-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Tue Jul 01 12:53:22 2014 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane.org Original-Received: from mail-vc0-f185.google.com ([209.85.220.185]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1X1vgf-0004qu-9R for gtp-pandoc-discuss@m.gmane.org; Tue, 01 Jul 2014 12:53:21 +0200 Original-Received: by mail-vc0-f185.google.com with SMTP id id10sf1993981vcb.2 for ; Tue, 01 Jul 2014 03:53:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; bh=yk5yNGXkh843Y1zrpTjZ4t09IlpjPiWofbKAS6mZ9nY=; b=xvKHZlvEe8QS+zaTez38bqBxlkP5coAYLqzm9lYj9qdrCUdt4EZOsK/BZBjGmGdbFd VwArwKquG1aniKenWKgDr5gMWMiGteH3WUZZbvqt80+Yidkni3kkiYdfvFJtWRIDmKxK ea9vfI9luJ0Px5hLlCPkXpEM7NONfhxS8CJGF0zUNL/5XmOxhioRbetsC+qOv/eM0Wid N6DCdEz942guKS86CuSFqzWHll423WhGIAKlS19BWLaci1CrexnXC6M7TJcBwYNlW7K9 vKYDR7/doF68QIibH1vGAkTiYgZSNur9jirwN2WVuNthTN4kb25Zz812b6wEwVNUkTn2 pRuQ== X-Received: by 10.140.37.150 with SMTP id r22mr125364qgr.3.1404212000538; Tue, 01 Jul 2014 03:53:20 -0700 (PDT) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 10.140.87.207 with SMTP id r73ls675905qgd.44.gmail; Tue, 01 Jul 2014 03:53:20 -0700 (PDT) X-Received: by 10.140.86.146 with SMTP id p18mr18685qgd.17.1404212000163; Tue, 01 Jul 2014 03:53:20 -0700 (PDT) In-Reply-To: <871tu6rto6.fsf-4GNroTWusrE@public.gmane.org> X-Original-Sender: jonathan-CY3SLAzk4Ga7P/GJLfOs3rVCufUGDwFn@public.gmane.org Precedence: list Mailing-list: list pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org; contact pandoc-discuss+owners-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-ID: X-Google-Group-Id: 1007024079513 List-Post: , List-Help: , List-Archive: Original-Sender: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-Subscribe: , List-Unsubscribe: , Xref: news.gmane.org gmane.text.pandoc:10231 Archived-At: ------=_Part_1332_4535905.1404211999507 Content-Type: text/plain; charset=UTF-8 On Monday, 30 June 2014 22:09:01 UTC+1, Jesse Rosenthal wrote: > > Sure -- at a certain point, you'd just have to put a div around the > blocks in the note, and let a filter do the dirty work. After all, > you're probably not submitting your manuscript in pandoc markdown. I'd > say marginnotes isn't that important, compared with foot- and end-. It > seems, pulling numbers entirely out of the air, that having just one > would cover 90% of cases, having two would cover about 99.5%, and having > three would cover 99.9%. Not sure if that's a good reason for stopping > at one, two, or three. > I suspect it would be more like 95% than 90%, but because of the nature of this list we're likely to be in the 5%. I'm normally in favour of increasing the expressive power of markdown, but this is a tricky one. For some people there might be a need to distinguish document endnotes from chapter endnotes. And then there's interaction with table footnotes, and the current MultiMarkdown inline footnote syntax to worry about. So I doubt we could properly cover all these options within the limits of the available ASCII. Perhaps it might be as useful to put some work into filters or pre-processors that parses an agreed coding for the 'footnote' markers, and turns them into the appropriate LaTeX/HTML/docx ... Perhaps: - Fnnn = footnotes - Ennn = endnotes - Mnnn = margin notes (possibly with MInnn/MOnnn to indicate inside/outside margin where that's important) - Cnnn = chapter notes -- You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/1546019c-186f-4a9c-ad6c-7166567c1b8d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. ------=_Part_1332_4535905.1404211999507 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Monday, 30 June 2014 22:09:01 UTC+1, Jesse Rosenthal w= rote:
Sure -- at a certain poin= t, you'd just have to put a div around the
blocks in the note, and let a filter do the dirty work. After all,
you're probably not submitting your manuscript in pandoc markdown. I'd
say marginnotes isn't that important, compared with foot- and end-. It
seems, pulling numbers entirely out of the air, that having just one
would cover 90% of cases, having two would cover about 99.5%, and havin= g
three would cover 99.9%. Not sure if that's a good reason for stopping
at one, two, or three.

I suspect it would be more like 95% th= an 90%, but because of the nature of this list we're likely to be in the 5%= . I'm normally in favour of increasing the expressive power of markdown, bu= t this is a tricky one. For some people there might be a need to distinguis= h document endnotes from chapter endnotes. And then there's interaction wit= h table footnotes, and the current MultiMarkdown inline footnote syntax to = worry about.  So I doubt we could properly cover all these options wit= hin the limits of the available ASCII.

Perhaps it = might be as useful to put some work into filters or pre-processors that par= ses an agreed coding for the 'footnote' markers, and turns them into the ap= propriate LaTeX/HTML/docx ...  Perhaps:
  • Fnnn =3D footnotes
  • Ennn =3D endnotes
  • Mnnn =3D margin notes (possibly with MInnn/MOnnn to indica= te inside/outside margin where that's important)
  • Cnnn =3D chapter notes

--
You received this message because you are subscribed to the Google Groups &= quot;pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to pand= oc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/= msgid/pandoc-discuss/1546019c-186f-4a9c-ad6c-7166567c1b8d%40googlegroups.co= m.
For more options, visit http= s://groups.google.com/d/optout.
------=_Part_1332_4535905.1404211999507--