Re: [NTG-context] Check for parity of pair tags on source file to be closed
On 1/10/20 1:46 PM, cont...@vivaldi.net wrote: > Hello Pablo, > > thanks for your suggestion. > > The "check" detected "\startitemize" which stayed open on the end of the > file, but did not detect "\if++" without correspondng "\fi". Hi Lukas, I don’t know whether checking for \if...\fi pairs is even implemented. Pablo -- http://www.ousia.tk ___ 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 ___
Re: [NTG-context] Epub export css buglets
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
___
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
___
Re: [NTG-context] Check for parity of pair tags on source file to be closed
Hello Pablo,
thanks for your suggestion.
The "check" detected "\startitemize" which stayed open on the end of the
file, but did not detect "\if++" without correspondng "\fi".
Thanks again -
Lukas
On 2020-01-09 13:08, Pablo Rodriguez wrote:
On 1/9/20 1:00 PM, cont...@vivaldi.net wrote:
Hello,
in most cases, when a source file is to be closed, pair elements
(tags)
should balanced.
This concerns e.g. { - }, \bgroup - \egroup, \startitemize -
\stopitemize, \if - \fi etc.
When we have a complicated project structure and when compiling the
topmost (root) source, a log for a disbalanced tag may appear, but the
unbalanced tag however may be difficult to find.
Is there a way to enable "watching" pair tags (at least mentioned
before) in the way that their disbalance would be reported (logged)?
Hi Lukas,
maybe this helps you:
mtxrunjit --autogenerate --script check file.tex
It only works with single files, since t doesn’t load other files (with
\input).
But it might fit your needs.
Just in case it helps,
Pablo
--
http://www.ousia.tk
\starttext
\if++
C
\stoptext
___
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
___
Re: [NTG-context] interline space default changed?
Thank you so much for the swift reply, Hans. Much appreciated. Hans Hagen writes: > On 1/9/2020 11:08 AM, Sandra Snan wrote: >> I was rerunning ConTeXt on some older documents and the interline space >> isn't the same. Sure, the new default looks great, but what was the old >> default? I need to match what I've already published. Thank you♥ > The interlinespace is defined in 'ex' units so it depends on that value > in the font that you use ... maybe the font changed? That's certainly possible. I switched computers and distros so all of those things might've been refreshed or altered upstream. I'm using Junicode for the main & bold but with Tex Gyre Schola for italic, and then grabbing miscellaneoussymbols out of a DejaVu Serif fallback and using DejaVu Sans Mono for mono (althought this particular page doesn't have any mono). If it isn't that case that those fonts have changed their metrics, which I wouldn't know, I'm kinda out of the loop generally (#unplugged), I was thinking that maybe the culprit could be that it used to work off of the italic's ex height and now works off of the main's ex height but that's just wild guessing on my part. I'm working around the problem by setting the interline space to 3.0675ex which makes the recompiled pages match the previously compiled pages exactly. (I don't know why that number. I found it by trying every number and seeing what matched.) The previously compiled pages didn't have an interline space set. Thanks again. Sandra ___ 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 ___
