From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: need help with markdown to epub convert
Date: Fri, 12 Nov 2021 10:12:54 -0500 [thread overview]
Message-ID: <e5cb4276-c79a-cc26-c776-2c7084ad53a6@usa.net> (raw)
In-Reply-To: <af1d0535-70c2-426d-a8dd-e4371c21c242n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
On 11/11/21 6:34 AM, mr vicky wrote:
> please can someone reply me here and help me to solve this issue
>
> On Sunday, November 7, 2021 at 12:31:44 PM UTC+5 mr vicky wrote:
>
> Dear All friends
> i am converting markdown to epub file using pandoc but there is a
> lot of image file name bellow every image which i want to remove.
> image file name looks like this
> image-BK7ECN82.jpg
> image-DOTWYQYC.jpg
> image-ZTFX0VRX.jpg
>
> kindly help me to remove these image file names from epub file
>
> 2. can i select word and make auto bold that word ? e.g my file have
> a lot of chapters and i want that every chapter heading should be
> bold and little bigger font size than normal text
>
> 3. is it possible that my table of contents which is showing in
> start of my book make clickable ?
I haven't played with ePub output, but I think think #1 could probably
be done by giving each image a title/caption - that is instead of
`![](image-BK7ECN82.jpg)` put `![Image Title](image-BK7ECN82.jpg)`
For the second, that probably needs to be changed in the CSS for the
ePub using `--css=`.
For the third - I don't know. Perhaps someone who's actually used the
ePub output will know.
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.
---------------------------------------------------------------
prev parent reply other threads:[~2021-11-12 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 7:31 mr vicky
[not found] ` <4f730a78-211a-48e7-ab44-abb2e28d3ca7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-11-11 11:34 ` mr vicky
[not found] ` <af1d0535-70c2-426d-a8dd-e4371c21c242n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-11-12 15:12 ` Daniel Staal [this message]
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=e5cb4276-c79a-cc26-c776-2c7084ad53a6@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).