Re: Markdown, tables and CSV

[Frank Colcord <frank-XCqNk0BTMejR7s880joybQ@public.gmane.org>]

[-- Attachment #1: Type: text/plain, Size: 5424 bytes --]

@sergio thanks for the pandoc filter. It looks very helpful. I don't know
python, but I can see how helpful that would be.
I've handled the csv in previous projects by changing the delimiters when
saving a spreadsheet so the delimiters are pandoc friendly.

@martin you say "The second step is then combining multiple Pandoc
documents into one. This can of course be done already". I've done this by
constructing long command line strings. I've also seen the preprocessors.
Is there another way to include multiple markdown files? I've been writing
in a wiki format where one txt file has links to others. I'd love to have
an automatic recursive way to include all the links as separate chapters.
If I have to, I don't mind setting up the includes manually. Please let me
know if you have seen documentation how to do that. I've seen some
documentation of recent pandoc versions which make it seem as if there are
some ways to do this.

I've seen this discussion:
https://groups.google.com/forum/#!searchin/pandoc-discuss/include/pandoc-discuss/eRuhx2Md0BI/mfzp_ZhuDAAJ

This discussion mentions preprocessors : FilePP and gpp.

have I missed some easier way to include files?

thanks, Frank



On 26 May 2016 at 09:04, Martin Fenner <martin.fenner-i39mICoz+qVg9hUCZPvPmw@public.gmane.org> wrote:

>
> Am 23.05.2016 um 23:22 schrieb John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>:
>
> But the Markdown philosophy is not about being "simple but
> powerful."  It's about having source files that are
> human-readable text files.
>
> Quoting from John Gruber's original Markdown syntax page:
>
> The overriding design goal for Markdown’s formatting syntax
> is to make it as readable as possible. The idea is that a
> Markdown-formatted document should be publishable as-is, as
> plain text, without looking like it’s been marked up with
> tags or formatting instructions.
>
>
> CSV is simple (though not as flexible as HTML formatting).
> But it doesn't pass this test.
>
> This design goal is really important to keep in mind when
> comparing Markdown to alternatives, which are often easier
> to write (because, for example, sublists are indicated by
> `**` instead of indentation), but don't look as natural
> to read.
>
>
> John, you are right, and I will rephrase. I think that seemless
> integration of markdown and CSV would make a lot of sense for many use
> cases. A Pandoc CSV reader is a good first step. The second step is then
> combining multiple Pandoc documents into one. This can of course be done
> already, but maybe extending the ![]() syntax would make it easier to
> import other documents (e.g. a number of tables in CSV format) into
> markdown documents instead of appending multiple documents into one. The
> only requirement would be that the external file referenced in ![]() would
> be in a format that Pandoc understands, otherwise it is loaded as binary
> blob, as for images.
>
>
> Am 26.05.2016 um 08:42 schrieb Sergio Correia <sergio.correia-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
>
> 2) For tables, I would also suggest to take a look at this filter:
>
> http://scorreia.com/software/panflute/guide.html#yaml-code-blocks
>
> It allows markdown like this:
>
> Some text
>
> ~~~ csv
> title: Some Title
> has-header: True
> ---
> Col1, Col2, Col3
> 1, 2, 3
> 10, 20, 30
> ~~~
>
> More text
>
>
> This combines pure CSV with options set up in YAML, so you can add
> captions and customize the table.
>
>
> I like the use of YAML in code blocks, as you frequently need additional
> metadata to properly understand tabular data (see for example
> http://data.okfn.org/doc/tabular-data-package). Very cool.
>
> Best,
>
> Martin
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "pandoc-discuss" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/pandoc-discuss/znGQ62WpWrg/unsubscribe.
> To unsubscribe from this group and all its topics, 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/B4779237-F368-454A-8E43-93EBCDFDF8AB%40datacite.org
> <https://groups.google.com/d/msgid/pandoc-discuss/B4779237-F368-454A-8E43-93EBCDFDF8AB%40datacite.org?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
frank-XCqNk0BTMejR7s880joybQ@public.gmane.org, cell: +447763116793, skype: colcord,
if you ever get no response, please send to: fcolcord-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org

-- 
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/CADZiF%2BX6AuYJEnnNCs1M%3Dspfbp9Fn4X2GBVkxXKp9g9SSNH16A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 8803 bytes --]