public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: H <agents-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Creating a partial HTML document
Date: Tue, 16 May 2023 21:07:19 -0400	[thread overview]
Message-ID: <6d105e0d-0e11-38fb-4978-9748102c93af@meddatainc.com> (raw)
In-Reply-To: <2ea6ffbc-e589-627c-4efe-b8e820cfd797-FcZObrvlYduBUy7/sJONFg@public.gmane.org>

On 05/16/2023 04:39 PM, H wrote:
> I did a test run and realize the following needs to be fixed to work for my use:
>
> Output:
>
> - pandoc inserts an id for each header that I have no need for and need to get rid of.
>
> - The output is wrapped at around 72 characters which I also do not want.
>
> - I need to have <div></div> tags added to meet the needed output format.
>
> - I need to have a style added to each HTML tag. These do not vary and could be predefined by me.
>
> - The output needs to be indented one level for each <div> level.
>
> Can I modify the pandoc processor to accomplish the above?
>
> Input:
>
> On another note, I would much prefer if I would not need to add an empty line between paragraphs in the markdown document to get the output processor to add <p></p> tags appropriately. A line break should suffice for pandoc to realize it's a new paragraph.
>
> Is this fixable by me?
>
> Thanks.
>
I found a solution to three of the items above:

- f markdown-auto_identifiers got rid of the identifiers although they were replaced by "class" instead.

- adding --section-divs added <section> although I would have preferred the older <div>

- adding --wrap=none allowed the output text in the HTML fragment to flow freely rather than break at 72 characters. The  latter made it harder for me to read the file.

Hoping that there are solutions to the rest of the items above but that might not be possible.

Oh, one more thing, my output is a HTML fragment and I was looking for an option to convert non-ASCII characters to the corresponding HTML entities. I understand that pandoc input is UTF8, as is the output, but an option to instead do the above conversion of the output would be very useful.

-- 
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/6d105e0d-0e11-38fb-4978-9748102c93af%40meddatainc.com.


  parent reply	other threads:[~2023-05-17  1:07 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
     [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 [this message]
     [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=6d105e0d-0e11-38fb-4978-9748102c93af@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).