public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: brainchild <ericlevy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: feedback needed for EPUB styling solution
Date: Tue, 17 Sep 2019 14:47:57 -0700 (PDT)	[thread overview]
Message-ID: <0e937dc2-728a-4d23-938d-412659ce16bf@googlegroups.com> (raw)


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

Several months ago, I started utilizing Pandoc for generating EPUB documents. 
My eventual hope was to generate polished-looking books from Markdown 
source, enhanced by custom cover art and styles. 

I began to notice difficulties making non-trivial style changes that were 
robust across readers and might be hoped to be stable over successive 
versions of Pandoc. I noticed also that even certain trivial changes were 
more difficult than might be reasonably desired.

The EPUB template and writer for Pandoc appear to be still in a relatively 
early state of maturity. Adding desired style depends largely on 
discovering the document structure of the output by examining it directly. 
The output is not globally structured according to a cogent and consistent 
design that is friendly to someone trying to add sophisticated or even 
moderately complex styling. Development efforts and users' understanding 
might be productively guided by a planned and documented design of how best 
to permit creation of style sheets that are robust and stable, yet simple 
and clear.

It was apparent to me that the best way to pursue this end was to introduce 
into the output a well-defined set of class tags, such that desired 
document elements could be easily selected by rules in style sheets. 
However, a broader set of considerations surround this issue.

I opened a discussion [1] in the issue tracker, and though it has received 
responses from John MacFarlane and another, it still lacks a breadth of 
responses necessary to determine which particular strategies might most 
compellingly serve those affected by the issue.

If you are affected by the issue, might benefit from enhancements related 
to it, have valuable experience in CSS or EPUB, or are otherwise in a 
position to provide useful opinions, please share your ideas.  Your 
contributions would be appreciated.

1. https://github.com/jgm/pandoc/issues/5749




-- 
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/0e937dc2-728a-4d23-938d-412659ce16bf%40googlegroups.com.

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

                 reply	other threads:[~2019-09-17 21:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=0e937dc2-728a-4d23-938d-412659ce16bf@googlegroups.com \
    --to=ericlevy-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).