From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Side Effects from HTML to HTML conversion
Date: Tue, 13 Apr 2021 09:25:38 -0400 [thread overview]
Message-ID: <950926c0-2980-d7c1-c8a0-c624a540d300@usa.net> (raw)
In-Reply-To: <40bf250d3cff42be22088054dc3fa618-aFO/2INALiozYggVrLCuDg@public.gmane.org>
On 4/13/21 2:57 AM, S. Manning wrote:
> If any of you can suggest a more appropriate tool than pandoc for my use
> case (take a HTML fragment and some metadata, wrap the fragment in
> header and footer text with some values inserted from the metadata to
> create a valid HTML file) I will consider it.
Honestly, the number of template engines of various complexities for
HTML may as well be infinite at this point. My first thought for this
would be to write it as a PHP file - the metadata locations would be
variables, process to HTML output - but pick a language and platform and
you'll be able to find a dozen.
Actually, my *first* thought for myself would be to use BBEdit's built
in template system. So, yeah - expand that to include most high-end
HTML editing software.
Daniel T. Staal
--
---------------------------------------------------------------
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------
next prev parent reply other threads:[~2021-04-13 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 6:57 S. Manning
[not found] ` <40bf250d3cff42be22088054dc3fa618-aFO/2INALiozYggVrLCuDg@public.gmane.org>
2021-04-13 13:25 ` Daniel Staal [this message]
[not found] ` <950926c0-2980-d7c1-c8a0-c624a540d300-Jdbf3xiKgS8@public.gmane.org>
2021-04-13 15:23 ` S. Manning
2021-04-13 21:53 ` John MacFarlane
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=950926c0-2980-d7c1-c8a0-c624a540d300@usa.net \
--to=dstaal-jdbf3xikgs8@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).