ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rik Kabel <ConTeXt@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: Epub export css buglets
Date: Fri, 17 Jan 2020 13:56:45 -0500	[thread overview]
Message-ID: <90931889-5d12-68ad-10a8-98440abe81ab@rik.users.panix.com> (raw)
In-Reply-To: <1ce8eb9b-c88b-eee0-28d0-39066501cff4@rik.users.panix.com>


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

On 1/10/2020 10:59, Rik Kabel wrote:
> 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).
>
The *namespace* and *text-width* issues are now fixed, but the 
*font-weight : italic* fault in default.css remains.

I also note that the W3C CSS validator reports for styles.css:

    11     document, div.document     inherited is not a hyphens value :
    inherited

That validator (and others) also report a number of issues for the 
@counter-style rule, which seems to have changed significantly since 
this CSS was developed. Validators report a number of smaller issues as 
well.

I understand that export output is a low-priority feature.

-- 
Rik



[-- Attachment #1.2: Type: text/html, Size: 2247 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
___________________________________________________________________________________

      reply	other threads:[~2020-01-17 18:56 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
2020-01-17 18:56     ` Rik Kabel [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=90931889-5d12-68ad-10a8-98440abe81ab@rik.users.panix.com \
    --to=context@rik.users.panix.com \
    --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).