From: H <agents-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Creating a partial HTML document
Date: Mon, 15 May 2023 16:52:51 -0400 [thread overview]
Message-ID: <d8c58326-c9a4-9a5b-973c-dea044654bda@meddatainc.com> (raw)
In-Reply-To: <256c5b57-18a8-4e45-94ee-0c1e2244f35en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 3953 bytes --]
On 05/15/2023 02:54 AM, ThomasH wrote:
> I suggest starting with the Getting Started document (https://pandoc.org/getting-started.html). As you still seem to be evaluating Pandoc as a tool, you might want to try it by running one of your typical markdown files through Pandoc (with `pandoc --from markdown --to html <filename>`) and look at the output. If that still looks promising, a good place for further study is the Pandoc User Guide (https://pandoc.org/MANUAL.html).
>
> On Monday, May 15, 2023 at 3:18:49 AM UTC+2 H wrote:
>
> On May 14, 2023 4:04:35 PM EDT, ThomasH <the...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >Creating document fragments is the default for HTML in Pandoc, you'd
> >have
> >to use the `--standalone` option to force it to create complete
> >documents
> >with header and footer. So that should meet your requirements.
> >
> >I don't know about indentation of the resulting HTML, much less so
> >about
> >your preferred indentation. But this is easy to find out and might be
> >helped by post-processing if it doesn't meet your expectations?
> >
> >I also cannot comment on Geany, but most editors have a way of running
> >an
> >external command on the current buffer or selected text.
> >
> >On Sunday, May 14, 2023 at 7:36:15 PM UTC+2 H wrote:
> >
> >I have a recurring need where I write markdown documents using my
> >favorite
> >editor, Geany, and then need to convert them to partial HTML documents.
> >
> >Partial because they lack the HTML file preamble and instead just start
> >
> >with <div> and end with the matching </div>.
> >
> >Each document contains one or more "sections", each also beginning with
> >a
> ><div> and ending with the matching </div>, and the conversion process
> >should be handle the sections, regardless of number.
> >
> >I like the resulting (partial) HTML document to use my preferred
> >indentation/white-space structure.
> >
> >Would pandoc be a good, perhaps the "best", tool for this? I should
> >also
> >add that I would like to run the conversion "process" from within
> >Geany.
>
> That sounds very promising. My markdown files use H1-4 for structuring and then text in paragraphs with strong or emphasis added as needed. I want to use this information when adding the HTML tags, together with style information for each tag that is predefined.
>
> I hope that Pandoc when encountering eg H2 in the markdown document would add the HTML tag and the predefined style information and the indent as I want it. No empty lines in the entire document but clear readable output.
>
> Would you have a specific suggestion where in the Pandoc documentation I start reading?
>
> --
> 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>.
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/256c5b57-18a8-4e45-94ee-0c1e2244f35en%40googlegroups.com <https://groups.google.com/d/msgid/pandoc-discuss/256c5b57-18a8-4e45-94ee-0c1e2244f35en%40googlegroups.com?utm_medium=email&utm_source=footer>.
Thank you, I will begin as you suggest.
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/d8c58326-c9a4-9a5b-973c-dea044654bda%40meddatainc.com.
[-- Attachment #2: Type: text/html, Size: 6531 bytes --]
next prev parent reply other threads:[~2023-05-15 20:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 17:36 H
[not found] ` <fefb43b9-ce9d-e2d9-9807-caaae90ebb14-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-14 20:04 ` ThomasH
[not found] ` <59aee5dc-9dbb-4c70-8f33-4c0722546638n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-15 1:18 ` H
[not found] ` <E19E3123-6FDC-4BD7-92CC-6BF1216B1E63-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-15 6:54 ` ThomasH
[not found] ` <256c5b57-18a8-4e45-94ee-0c1e2244f35en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-15 20:52 ` H [this message]
[not found] ` <d8c58326-c9a4-9a5b-973c-dea044654bda-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-16 20:39 ` H
[not found] ` <2ea6ffbc-e589-627c-4efe-b8e820cfd797-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-17 1:07 ` H
[not found] ` <6d105e0d-0e11-38fb-4978-9748102c93af-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-17 5:14 ` ThomasH
[not found] ` <39c3adec-4363-43be-ac1f-76e96aeead65n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-17 7:40 ` Bastien DUMONT
2023-05-17 23:35 ` H
[not found] ` <6fc811c0-27dd-29e8-936c-59e5262dff7e-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-19 6:57 ` ThomasH
2023-05-17 23:40 ` H
2023-05-17 18:45 ` John MacFarlane
[not found] ` <1C388813-0134-4592-BABD-0B0EA3D90CE4-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-05-17 23:29 ` H
[not found] ` <d4d83813-44aa-83bc-94d0-6d30f3d66ef9-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-29 9:43 ` BPJ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d8c58326-c9a4-9a5b-973c-dea044654bda@meddatainc.com \
--to=agents-fczobrvlydubuy7/sjonfg@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).