From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/23433 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: brainchild Newsgroups: gmane.text.pandoc Subject: feedback needed for EPUB styling solution Date: Tue, 17 Sep 2019 14:47:57 -0700 (PDT) Message-ID: <0e937dc2-728a-4d23-938d-412659ce16bf@googlegroups.com> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_3051_767707801.1568756877079" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="115020"; mail-complaints-to="usenet@blaine.gmane.org" To: pandoc-discuss Original-X-From: pandoc-discuss+bncBCK6XHV3WYGBBDVJQXWAKGQE3ZS56FA-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Tue Sep 17 23:48:03 2019 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane.org Original-Received: from mail-oi1-f185.google.com ([209.85.167.185]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1iALKK-000Tjl-RM for gtp-pandoc-discuss@m.gmane.org; Tue, 17 Sep 2019 23:48:01 +0200 Original-Received: by mail-oi1-f185.google.com with SMTP id d206sf2499284oig.6 for ; Tue, 17 Sep 2019 14:48:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20161025; h=sender:date:from:to:message-id:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=1tQghznc9ojZW/kRtHO0aOqDiEbRGsClcezfS7vPy4Y=; b=aexKbnsDAyZl7vs3kWjh/Lx/Zk7OENaxyVFmuI6zEFoGZdzGyIW1lo0ZtrT5gJ5IjM Hqz0gDcqWfAR69n4CL+dCIQ7BkZ6nS/k6Ay5xEiL5gs0bEWl2lYNHIwY22eXuuQ6XOzg ZPYekkb3ZbHiupqzVZntX8zITwv3H6O7npYkhUSk7jn9nPW6I4iTyqcxZWbSgu2u0KIE DiHLuIBVkKy3Lr4O6fHcXVO0ydrZPhlebs3wg7nSpV/nC77PIEcNBh2CugM+UKjTNpyc lE9GbPtqokBLpq/H1Qpd+3wcQRrkYRZ+9Q5polxm31NhdWTKTbVzrfX0QQBtQGIAVEPx 48QQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:subject:mime-version:x-original-sender :reply-to:precedence:mailing-list:list-id:list-post:list-help :list-archive:list-subscribe:list-unsubscribe; bh=1tQghznc9ojZW/kRtHO0aOqDiEbRGsClcezfS7vPy4Y=; b=O0yjE9XVnepHrO7XpCXRuu9qkMs8jiOw189msR8QGjJpHNRIZ2/Fgm1ZFx/9/HaDrd R5Ngr9P+dDWNs8UMTzH5u9n7e9FWMMD0TjDJPmGMlGOgip/CKDPBtxoaXylZtToROETI rQ2hFdFI8HnXBIT1EXBnS+xl2YJsrYF+N8Ym2AxTKtqEv7xIZ95XKMQfgVgwtzFqJG+j zPXu1vDVXX/a462j5Gb4Kqh5axlXIRzr/CNh3TQgK49wso0wBMlws+uVLdhf9N2ovGwh JR7KJIwWb+Oi9rqi6ssH35pCH3f8uU7gltWipzWWOnTEIVIMu1rnvlX/DeaAz2vj2i0O CqWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=sender:x-gm-message-state:date:from:to:message-id:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=1tQghznc9ojZW/kRtHO0aOqDiEbRGsClcezfS7vPy4Y=; b=fqSzr+dZEDuMQ8hGMk0RzAY2TohRmr6SbsvzdUCiPvfp1/MbFMFbi/SoSLRFqXyD5l 5PIITnHWgb2sDCud571IO2Wzrp8zruarpLcYGHZN1PnAcY1IIcjIE+9rYCCs7J2EzPTF OlhnL7vfOQ93j3c2IjbLaKNS9wvz47IneArFSxK5uqYf369uakw9ZHezqqOLNZ99cOlw 3rqeD+a8tOJvTN1TFLCZp3FRvMWh9TVWSsWZRjnxB4nxiNksVvoOdU0SjiePVEQX0YjC Jk+LiWoukcYPwQNaFElhlB9YIYGwRINGzT0E4MSpCtX5wA4+zGF1LSKoWO7AWwkxFXyD Idug== Original-Sender: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org X-Gm-Message-State: APjAAAWPxSJvmocEISgVu6Usv5gkQXN2NMPoNsmdDJEMlOoeTXyZJI4z AE0NwDz/Cqaf+yuCR2NGFsc= X-Google-Smtp-Source: APXvYqzptqwxUUhj9Ktk3eT2H+qubGdsuUHsFGa/nqPxuoUGyjmrpDnlN3E7Qt+nlghCurLEK/hcyA== X-Received: by 2002:aca:6203:: with SMTP id w3mr196677oib.142.1568756879192; Tue, 17 Sep 2019 14:47:59 -0700 (PDT) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 2002:a54:4f98:: with SMTP id g24ls56183oiy.12.gmail; Tue, 17 Sep 2019 14:47:58 -0700 (PDT) X-Received: by 2002:aca:3ad6:: with SMTP id h205mr171496oia.129.1568756877768; Tue, 17 Sep 2019 14:47:57 -0700 (PDT) X-Original-Sender: ericlevy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org Precedence: list Mailing-list: list pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org; contact pandoc-discuss+owners-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-ID: X-Google-Group-Id: 1007024079513 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Xref: news.gmane.org gmane.text.pandoc:23433 Archived-At: ------=_Part_3051_767707801.1568756877079 Content-Type: multipart/alternative; boundary="----=_Part_3052_292723468.1568756877080" ------=_Part_3052_292723468.1568756877080 Content-Type: text/plain; charset="UTF-8" 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. ------=_Part_3052_292723468.1568756877080 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Several months ago, I started utilizing Pan= doc for generating EPUB=C2=A0documents. My eventual h= ope was to generate polished-looking books from=C2=A0= Markdown source, enhanced by custom cover art and styles.=C2=A0

I began to notice difficulties making non-trivial style changes that= =C2=A0were robust across readers and might be hoped t= o be stable over=C2=A0successive versions of Pandoc. = I noticed also that even certain trivial=C2=A0changes= were more difficult than might be reasonably desired.
<= br style=3D"caret-color: rgb(48, 48, 48); color: rgb(48, 48, 48); font-fami= ly: monospace; font-size: 13.3333px; -webkit-tap-highlight-color: rgba(0, 0= , 0, 0.4);">The EPUB template and writer for Pandoc appear t= o be still in a=C2=A0relatively early state of maturi= ty. Adding desired style depends=C2=A0largely on disc= overing the document structure of the output by=C2=A0= examining it directly. The output is not globally structured according=C2= =A0to a cogent and consistent design that is friendly= to someone trying to=C2=A0add sophisticated or even = moderately complex styling. Development=C2=A0efforts = and users' understanding might be productively guided by a=C2=A0= planned and documented design of how best to permit creation= of style=C2=A0sheets that are robust and stable, yet= simple and clear.

It was ap= parent to me that the best way to pursue this end was to=C2=A0introduce into the output a well-defined set of class tags, such t= hat=C2=A0desired document elements could be easily se= lected by rules in style=C2=A0sheets. However, a broa= der set of considerations surround this issue.

I opened a discussion [1] in the issue tracker, and thou= gh it has=C2=A0received responses from John MacFarlan= e and another, it still lacks a=C2=A0breadth of respo= nses necessary to determine which particular strategies=C2=A0might most compellingly serve those affected by the issue.
If you are affected by the issue, mi= ght benefit from enhancements=C2=A0related to it, hav= e valuable experience in CSS or EPUB, or are=C2=A0oth= erwise in a position to provide useful opinions, please share your=C2=A0ideas.=C2=A0 Your contributions would be appreciated.

1.=C2=A0https://github.com/jgm/pandoc/issues/5749




--
You received this message because you are subscribed to the Google Groups &= quot;pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to pand= oc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@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.co= m.
------=_Part_3052_292723468.1568756877080-- ------=_Part_3051_767707801.1568756877079--