From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/16018 Path: news.gmane.org!.POSTED!not-for-mail From: Sergio Correia Newsgroups: gmane.text.pandoc Subject: Re: Markdown, tables and CSV Date: Mon, 14 Nov 2016 17:33:02 -0800 (PST) Message-ID: <12c01cfd-f9de-4dd9-bb80-fcac75c808be@googlegroups.com> References: <047d7b86ebe83c062b05332eab9b@google.com> <20BF19CB-A2B0-4B19-A749-D750CDD89736@martinfenner.org> <14b8fa54-dc04-4874-bf47-fb268fc9f298@googlegroups.com> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1798_785874717.1479173582854" X-Trace: blaine.gmane.org 1479173606 24840 195.159.176.226 (15 Nov 2016 01:33:26 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 15 Nov 2016 01:33:26 +0000 (UTC) To: pandoc-discuss Original-X-From: pandoc-discuss+bncBCOYT6WP5QGRBT6LVHAQKGQE6PB46NA-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Tue Nov 15 02:33:21 2016 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane.org Original-Received: from mail-qk0-f186.google.com ([209.85.220.186]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c6ScP-00043H-Ae for gtp-pandoc-discuss@m.gmane.org; Tue, 15 Nov 2016 02:33:01 +0100 Original-Received: by mail-qk0-f186.google.com with SMTP id 124sf18677697qkh.1 for ; Mon, 14 Nov 2016 17:33:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=sender:date:from:to:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=zQ2doO/ho5o+oR5tNNlskNXjoLh744Aqupvcd8bsN/E=; b=xxEKtAH2MZ2dmJOHHjxtgpHtlGnwwVBuflgsO1nZryAue08MsBov9rBheis7n4gaf7 bxKdeX4fmPF7L1jh7JN4dz9XdqTljBE8h9C2ICvQkBxUSqqM+2l976uApx3eMkA7WAMi 5XRSYRIFBvzup6+j+ejJ57NW697uinsHiWzLiXQ8FB+1iRjqF91LSRD7t482up1seQf/ c9uPaGEY3L3GEY6Nq4CLuDkrBJFwLD4gIdJNjql3xMvd/dvY2DNO0DKxXQmpyaeR15oQ TVkHhFgM/yGS4x8/rYfbxTVqRk3iv9W6fa0blemO/JjM8f57UkXOcf2GzuN4YLpRpgiT DMHg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=zQ2doO/ho5o+oR5tNNlskNXjoLh744Aqupvcd8bsN/E=; b=zGFXRPe7XQ/Z1DzRHEARzZk/CYHIlTkviUbiVC6mg1Pbc+kDdFD3pLeco/JbOLrQFV SLfCrMymhC7HlA4MgZaNXK/a9jB0samDtru+fWgvQ20Z6/o+M8hPdNONi1ckbTf16Odi aAak8tqcygnnU6n8GWfqiSpEfsiUed85FOkxY909W9kdKuoTzDprzzxsIelFt8laJfia y3fjk0JJ5xvcZA89O4dOKi8VgCa1QRJ5/jve5ZYH9x7w+vESUHCJKA5KmU39854G9oh/ r+Z9tqWJFGwpiacUN6JJaKuf21ZqHkv8UKiWkU1thD2qUW8yMcZI1KsC3U2h3vjyi/3O Aoxw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=sender:x-gm-message-state:date:from:to:message-id:in-reply-to :references:subject:mime-version:x-original-sender:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=zQ2doO/ho5o+oR5tNNlskNXjoLh744Aqupvcd8bsN/E=; b=a7JN/E5yEkyanIvyt9ypulEKrxuHqMGdI4EOEt66VChQmv2ALAXu0t65qvBFncsu7K Gtt0PIIYviWWrVys6nMws7joyWYNB15D7E9FsIKjM2f2h2ji4AC4aNoPKrAc+HC6cD3O vY2XgsEG/yJUyI4mvgDDbq2vtAlzumnORFbLCABT3fTJOLvDSf484i9fwAeRnpfZ3lP7 k3D/xQmjimxNcezwKjgxaMvnj0uOW17hAVr5deDgPpXhZTPL2i/Vj2sXhcDEbibYw4oh L9TAVwCbu3XpufBJ4E5psR1gCCKkSjLuSFKOnqXJu6g/rmlT0OPhWUKm59wMC7LmtGgW oGfQ== Original-Sender: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org X-Gm-Message-State: ABUngve3VrRZoDxJNzVBUIKmQ/s+nrPBEHwnAwR6YmYbC4xWODt8ah5Om0xCAaReCE/C0Q== X-Received: by 10.157.15.143 with SMTP id d15mr1281398otd.2.1479173584181; Mon, 14 Nov 2016 17:33:04 -0800 (PST) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 10.157.14.179 with SMTP id 48ls7912093otj.31.gmail; Mon, 14 Nov 2016 17:33:03 -0800 (PST) X-Received: by 10.157.37.247 with SMTP id q110mr1282110ota.5.1479173583582; Mon, 14 Nov 2016 17:33:03 -0800 (PST) In-Reply-To: X-Original-Sender: sergio.correia-Re5JQEeQqe8AvxtiuMwx3w@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: , List-Unsubscribe: , Xref: news.gmane.org gmane.text.pandoc:16018 Archived-At: ------=_Part_1798_785874717.1479173582854 Content-Type: multipart/alternative; boundary="----=_Part_1799_467093631.1479173582855" ------=_Part_1799_467093631.1479173582855 Content-Type: text/plain; charset=UTF-8 On Monday, November 14, 2016 at 9:38:48 AM UTC-5, BP wrote: > > One possible problem with including metadata as YAML is that it may become > harder for filters earlier in the chain to query the metadata or inject a > CSV block using the normal attribute interface, if any, of the filter > engine, not to mention parsing the CSV, query or alter it and write it > back. For that reason I think it be better if the content of the code block > is the pure CSV data. FWIW I tried both strategies with my unpublished > filters, so I'm not just speculating. > > Also since there are many filters doing the same thing the identifying > class should better not be just `csv` but also identify the filter expected > to handle the data. > Sorry, I don't understand what is the problem. CSV blocks are not a standard feature of Pandoc, and each filter has its own conventions, so I don't think is reasonable to expect a new filter to allow its data to be queried/exposed to other, unknown filters. About having additional information besides the raw CSV, I think it's actually the most important thing, because it allows you to have a title, to load CSV from external sources, add footnotes, and specify output options, all of which wouldn't be possible if we restricted the content to be some CSV-delimited info. Finally, I do agree that having a filter named "csv" or "pandoc-csv" might collide with existing filters, but I don't think there is a problem with having a csv class. I think the chance that a user ends up requiring two different filters that use CSV code blocks is low enough for this to be a non-issue. -- 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/12c01cfd-f9de-4dd9-bb80-fcac75c808be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. ------=_Part_1799_467093631.1479173582855 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Monday, November 14, 2016 at 9:38:48 AM UTC-5, = BP wrote:

One po= ssible problem with including metadata as YAML is that it may become harder= for filters earlier in the chain to query the metadata or inject a CSV blo= ck using the normal attribute interface, if any, of the filter engine, not = to mention parsing the CSV, query or alter it and write it back. For that r= eason I think it be better if the content of the code block is the pure CSV= data. FWIW I tried both strategies with my unpublished filters, so I'm= not just speculating.

Also since there are many filters doing the same thing the i= dentifying class should better not be just `csv` but also identify the filt= er expected to handle the data.


Sorry, = I don't understand what is the problem. CSV blocks are not a standard f= eature of Pandoc, and each filter has its own conventions, so I don't t= hink is reasonable to expect a new filter to allow its data to be queried/e= xposed to other, unknown filters.

About having add= itional information besides the raw CSV, I think it's actually the most= important thing, because it allows you to have a title, to load CSV from e= xternal sources, add footnotes, and specify output options, all of which wo= uldn't be possible if we restricted the content to be some CSV-delimite= d info.

Finally, I do agree that having a filter n= amed "csv" or "pandoc-csv" might collide with existing = filters, but I don't think there is a problem with having a csv class. = I think the chance that a user ends up requiring two different filters that= use CSV code blocks is low enough for this to be a non-issue.

--
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/12c01cfd-f9de-4dd9-bb80-fcac75c808be%40googlegroups.co= m.
For more options, visit http= s://groups.google.com/d/optout.
------=_Part_1799_467093631.1479173582855-- ------=_Part_1798_785874717.1479173582854--