public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Mario Valle <siliconvalley58-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: ebook styling for footnote back mark
Date: Sun, 29 Jan 2017 20:41:32 -0800 (PST)	[thread overview]
Message-ID: <b677ade2-88f9-4852-81a4-01673f3c3bd5@googlegroups.com> (raw)
In-Reply-To: <e0969fc5-6a11-4a1a-b946-9083b2f72f7d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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

Adding these two lines solved the problem. But, is there a better solution 
for the back mark?
.footnoteRef {color: #DC143C}
.footnotes ol li p a:last-child {color: #DC143C}



Il giorno lunedì 30 gennaio 2017 05:32:19 UTC+1, Mario Valle ha scritto:
>
> Dear pandoc gurus,
> I need to style footnote ref and footnote back mark (↩) in ebook2 output 
> because in Apple's iBook application they are not distinguishable from 
> normal text.
> No problem for footnote ref. It has class footnoteRef that I can define in 
> css. But the back mark has no distinguishable feature and I don't know how 
> to style it to make clear it is a link. Is it possible to add a class (like 
> footnoteBack) to it? Or should I resort to :last-child css3 selector if it 
> is supported in epub2?
> Thanks for your help!
> mario
>

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/b677ade2-88f9-4852-81a4-01673f3c3bd5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

  parent reply	other threads:[~2017-01-30  4:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30  4:32 Mario Valle
     [not found] ` <e0969fc5-6a11-4a1a-b946-9083b2f72f7d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-30  4:41   ` Mario Valle [this message]
2017-01-30  9:21   ` 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=b677ade2-88f9-4852-81a4-01673f3c3bd5@googlegroups.com \
    --to=siliconvalley58-re5jqeeqqe8avxtiumwx3w@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).