From: Rik Kabel <ConTeXt@rik.users.panix.com>
To: Hans Hagen <j.hagen@xs4all.nl>,
"ntg-context@ntg.nl >> mailing list for ConTeXt users"
<ntg-context@ntg.nl>
Subject: Re: Epub export css buglets
Date: Fri, 10 Jan 2020 10:59:20 -0500 [thread overview]
Message-ID: <1ce8eb9b-c88b-eee0-28d0-39066501cff4@rik.users.panix.com> (raw)
In-Reply-To: <ee031466-708b-5a42-b638-213d758cd1b2@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2062 bytes --]
On 1/9/2020 11:25, Hans Hagen wrote:
> On 1/6/2020 7:08 PM, Rik Kabel wrote:
>> A couple of small issues with the css for epub output.
>>
>> First, back-exp.lua creates, in \jobname-styles.css
>>
>> @namespace context url('%namespace%') ;
>>
>> This should probably be:
>>
>> @namespace context url('http://www.pragma-ade.com/context/export') ;
>>
>> That file also has:
>>
>> document,
>> %namespace%div.document {
>> font-size : %size% !important ;
>> max-width : %width% !important ;
>> text-width : %align% !important ;
>> hyphens : %hyphens% !important ;
>> }
>>
>> which contains the invalid css property text-width. Perhaps that
>> should be text-align or text-justify.
>>
>> Something else appears to be creating, in \jobname-defaults.css:
>>
>> pubfld[detail="title"],
>> div.pubfld.title {
>> display : inline ;
>> font-weight : italic ;
>> }
>>
>> which incorrectly assigns italic to font-weight when of course it is
>> a font-style as far as css is concerned. This can be seen in file
>> export-example.css in the distribution.
> can you make a mwe ...
>
Here ya go, about as minimal as I can imagine:
\setupbackend [export=yes]
\setupexport []
\starttext
!
\stoptext
and in the resulting export styles directory, I get:
g:\yoiks-export\styles>grep "namespace\|weight.*italic\|text-width" *.css
yoiks-defaults.css:@namespace context url('http://www.pragma-ade.com/context/export') ;
yoiks-defaults.css: font-weight : italic ;
yoiks-images.css:@namespace context url('%namespace%') ;
yoiks-styles.css:@namespace context url('%namespace%') ;
yoiks-styles.css: text-width : justify !important ;
yoiks-templates.css:@namespace context url('%namespace%') ;
So:
* three unexpanded %namespace%s,
* one invalid property (text-width),
* and one incorrect property (font-weight should be font-style).
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 3265 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-01-10 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 18:08 Rik Kabel
2020-01-09 16:25 ` Hans Hagen
2020-01-10 15:59 ` Rik Kabel [this message]
2020-01-17 18:56 ` Rik Kabel
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=1ce8eb9b-c88b-eee0-28d0-39066501cff4@rik.users.panix.com \
--to=context@rik.users.panix.com \
--cc=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
/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).