public inbox archive for
 help / color / mirror / Atom feed
From: almaghfuur lahu <>
To: pandoc-discuss <pandoc-discuss-/>
Subject: Need pandoc to create a latex file from some html files
Date: Sun, 26 Nov 2023 16:12:58 -0800 (PST)	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 1308 bytes --]

How do we create a new PDF file by having pandoc to create a latex file 
from some html files under one directory merely, i.e. not recursively, as 
it's just acquired from a server directory to display a rather simple, 
small reference documentation?
$ ls
cover.png  errata.html  index.html  manual.html

index.html is actually containing table of contents, each line of which is 
a link to a location in the file manual.html, and also some words index , 
each line of which is a link to a location in manual.html

It has line:

<IMG SRC="cover.png" ALT="" TITLE="click to buy the book" BORDER=1 
ALIGN="left" HSPACE=12>

manual.html is the content or body of the reference manual

errata.html is the catch up of corrections needed to care in this reference 
How to accomplish to obtain its one analogous latex file from which its PDF 
file can be created the best, most efficient way ?

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/
To view this discussion on the web visit

[-- Attachment #1.2: Type: text/html, Size: 8496 bytes --]

             reply	other threads:[~2023-11-27  0:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27  0:12 almaghfuur lahu [this message]
     [not found] ` <aaec9ee1-c839-4dd6-bd56-c41657991b6en-/>
2023-11-27  8:35   ` Need pandoc to create a latex file, " Bastien DUMONT
2023-11-28  2:37     ` almaghfuur lahu
2023-11-28 18:24   ` Need pandoc to create a latex file " BP Jonsson

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \
    --cc=pandoc-discuss-/ \

* 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).