Re: [NTG-context] pgfplots module wrecks in latest
On Fri, 30 Dec 2022, Hans Hagen via ntg-context wrote:
> On 12/30/2022 12:40 AM, Gavin via ntg-context wrote:
> > Hi List,
> >
> > The TikZ related module “pgfplots” is causing a fatal error in the latest
> > ConTeXt. Here is a MWE:
> >
> >
> > \usemodule[tikz]
> > \usemodule[pgfplots]% PGFPlots module for graphs
> >
> > \starttext
> >
> > \starttikzpicture
> > \draw (0, 0) circle (3cm);
> > \stoptikzpicture
> >
> > \stoptext
> >
> >
> > Without loading the pgfplots module, this draws a circle. With the
> > \usemodule[pgfplots] line, this has the error below before doing anything.
> >
> > I don’t know when this started happening, because I don’t use pgfplots
> > often, but it was probably in the last couple months.
> >
> > Thanks for all the great updates!
> these extra modules have bad loaders ... i'll send you better ones to test
pgfplots still appears to be broken in LMTX:
\usemodule[pgfplots]
\starttext
Hello
\stoptext
gives
tex error > tex error on line 521 in file pgfplots.code.tex: Use of
\pgfplots@command@to@string@@ doesn't match its definition
m
acro:colormap
\pgfplots@colormap@catcodemagic
\pgfplots@command@to@string
#1#2->\expandafter \pgfplots@command@to@string@@ \meaning #1
\pgfplots@EOI {#2}
\pgfplots@command@to@string\pgfplots@colormap@catcodemagic\pgfplots@colormap@catcodemagic
@Hans, could you please send me the new loaders as well and I can test them.
Thanks,
Aditya___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] question about multimedia renderings
On Sun Jan 15, 2023 at 10:49 PM CET, Pablo Rodriguez via ntg-context wrote:
> Dear list,
>
> I’m planning to add an explanation about multimedia inclusion to the
> wiki, but first I wanted to discuss an issue I have found.
>
> I have the following sample (adapted from scrn-wid.mklx):
>
> \setupinteraction[state=start]
> \starttext
> \null\page
> \definerenderingwindow[myrenderingwindow]
> [width=\textwidth, height=\textwidth,
> %openpageaction=StartCurrentRendering,
> %closepageaction=StopCurrentRendering,
> openpageaction=StartRendering{\currentrendering},
> closepageaction=StopRendering{\currentrendering},
> framecolor=red]
> \startTEXpage[offset=1em, pagestate=start]
> \userendering[key-name][video/mp4][video.mp4]
> [embed=yes,
> auto,
> ]
> \placerenderingwindow[myrenderingwindow][key-name]
> \stopTEXpage
> \null\page
> \stoptext
>
> \userendering[][][auto] would enable automatic play or stop when the
> page with the rendering is reached or left (respectively).
>
> I cannot get it working. Neither do work the commented lines in
> \definerenderingwindow.
>
> Inspecting the PDF code, the screen annotation only gets an additional
> actions dictionary
> (https://opensource.adobe.com/dc-acrobat-sdk-docs/standards/pdfstandards/pdf/PDF32000_2008.pdf#G11.2096829)
> with /PO and /PC entries, when open and close page actions are set to
> StartRendering{\currentrendering} and StopRendering{\currentrendering}.
>
> Just for reference, this is the screen annotation object with the
> additional actions dictionary:
>
> 13 0 obj
> <<
> /Type /Annot
> /A <<
> /AN 13 0 R
> /OP 0
> /R 12 0 R
> /S /Rendition
> >>
> /AA <<
> /PC <<
> /AN 13 0 R
> /OP 1
> /R 12 0 R
> /S /Rendition
> >>
> /PO <<
> /AN 13 0 R
> /OP 0
> /R 12 0 R
> /S /Rendition
> >>
> >>
> /Border [ 0 0 0 ]
> /P 14 0 R
> /Subtype /Screen
> /T
> /Rect [ 12.353668 12.353668 437.54664 437.54664 ]
> >>
> endobj
>
> And this is what I get with \userendering[][][auto]:
>
> 13 0 obj
> <<
> /Type /Annot
> /A <<
> /AN 13 0 R
> /OP 0
> /R 12 0 R
> /S /Rendition
> >>
> /Border [ 0 0 0 ]
> /P 14 0 R
> /Subtype /Screen
> /T
> /Rect [ 12.353668 12.353668 437.54664 437.54664 ]
> >>
> endobj
>
> Could anyone be so kind to confirm the issue?
AFAICT I based the auto option on the "Start/StopCurrentRendering"
actions (2021-09-14) which we later agreed to remove (2021-09-17), so
there was a bug. Reasoning for removal of the "Current" variants at the
time:
On Tue Sep 14, 2021 at 9:37 PM CEST, Hans Hagen wrote:
> Because \currentrendering is local we could as well drop the Current
> variants ... it's not like people will put hundreds of videos in a file
> so enforcing the named one makes sense.
So Start/StopRendering{label} should be used instead (Hans already redid
most of the examples, you found the two places in scrn-wid.mklx where
there is an incosistency.
I would think that something like the attached could work. But in some
cases it fails on the TeX side with something I am not sure about. I
probably overlooked something. Anyways the idea is to just use the
Start/StopRendering actions with the correct label.
Michal
if not modules then modules = { } end modules ['lpdf-wid'] = {
version = 1.001,
comment = "companion to lpdf-ini.mkiv",
author= "Hans Hagen, PRAGMA-ADE, Hasselt NL",
copyright = "PRAGMA ADE / ConTeXt Development Team",
license = "see context related readme files"
}
-- It's about time to give up on media in pdf and admit that pdf lost it to
html.
-- First we had movies and sound, quite easy to deal with, but obsolete now.
Then we
-- had renditions but they turned out to be unreliable from the start and look
-- obsolete too or at least they are bound to the (obsolete) flash technology
for
-- rendering. They were already complex constructs. Now we have rich media which
-- instead of providing a robust future proof framework for general media types
-- again seems to depend on viewers built in (yes, also kind of obsolete) flash
-- technology, and we cannot expect this non-open technology to show up in open
-- browsers. So, in the end we can best just use links to external resources to
be
-- future proof. Just look at the viewer preferences pane to see how fragile
support
-- is. Interestingly u3d support is kind of built in, while e.g. mp4 support
relies
-- on wrapping in swf. We used to stay ahead of the pack with support of the
fancy
-- pdf features but it backfires and is not worth the trouble. And yes, for
control
-- (even simple like starting and stopping videos) one has to revert to
JavaScript,
-- the other fragile bit. And, now that adobe quits flash in 2020 we're without
any
-- video anyway. Also, it won't play on all platforms and
[NTG-context] question about multimedia renderings
Dear list,
I’m planning to add an explanation about multimedia inclusion to the
wiki, but first I wanted to discuss an issue I have found.
I have the following sample (adapted from scrn-wid.mklx):
\setupinteraction[state=start]
\starttext
\null\page
\definerenderingwindow[myrenderingwindow]
[width=\textwidth, height=\textwidth,
%openpageaction=StartCurrentRendering,
%closepageaction=StopCurrentRendering,
openpageaction=StartRendering{\currentrendering},
closepageaction=StopRendering{\currentrendering},
framecolor=red]
\startTEXpage[offset=1em, pagestate=start]
\userendering[key-name][video/mp4][video.mp4]
[embed=yes,
auto,
]
\placerenderingwindow[myrenderingwindow][key-name]
\stopTEXpage
\null\page
\stoptext
\userendering[][][auto] would enable automatic play or stop when the
page with the rendering is reached or left (respectively).
I cannot get it working. Neither do work the commented lines in
\definerenderingwindow.
Inspecting the PDF code, the screen annotation only gets an additional
actions dictionary
(https://opensource.adobe.com/dc-acrobat-sdk-docs/standards/pdfstandards/pdf/PDF32000_2008.pdf#G11.2096829)
with /PO and /PC entries, when open and close page actions are set to
StartRendering{\currentrendering} and StopRendering{\currentrendering}.
Just for reference, this is the screen annotation object with the
additional actions dictionary:
13 0 obj
<<
/Type /Annot
/A <<
/AN 13 0 R
/OP 0
/R 12 0 R
/S /Rendition
>>
/AA <<
/PC <<
/AN 13 0 R
/OP 1
/R 12 0 R
/S /Rendition
>>
/PO <<
/AN 13 0 R
/OP 0
/R 12 0 R
/S /Rendition
>>
>>
/Border [ 0 0 0 ]
/P 14 0 R
/Subtype /Screen
/T
/Rect [ 12.353668 12.353668 437.54664 437.54664 ]
>>
endobj
And this is what I get with \userendering[][][auto]:
13 0 obj
<<
/Type /Annot
/A <<
/AN 13 0 R
/OP 0
/R 12 0 R
/S /Rendition
>>
/Border [ 0 0 0 ]
/P 14 0 R
/Subtype /Screen
/T
/Rect [ 12.353668 12.353668 437.54664 437.54664 ]
>>
endobj
Could anyone be so kind to confirm the issue?
Many thanks for your help,
Pablo
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Is the Society of Biblical Literature (SBL) style files for ConTeXt incompatible with \setupinteraction[state=start]?
On 1/15/23 17:57, Joel via ntg-context wrote:
> When I am using the SBL ConTeXt files for citations, if I add a line
> `\setupinteraction[state=start` my code starts complaining:
> [...]
> Is this package incompatible with interaction?
Hi Joel,
unless I’m missing your point,
https://github.com/jjmccollum/context-sbl/issues/new is the place to
report your issue.
BTW, I downloaded current master
(https://github.com/jjmccollum/context-sbl/archive/refs/heads/main.zip)
and the test file compiles just fine with and without
\setupinteraction[state=start].
The undefined command from your error message (\currentbtxloctext) seems
to be defined in four setups from tex/publ-imp-sbl.mkvi:
\def\currentbtxloctext{\btxparameter{loctext}}
The setups containing the definitions are btx:sbl:cite:inlinelong,
btx:sbl:cite:inlineshort, btx:sbl:cite:inline and btx:sbl:cite:shorthand.
Your code might be triggering an unwanted effect and the module
developer may fix it.
Just in case it might help,
Pablo
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Why does \doifsomething think there is content?
On Sun, 15 Jan 2023, Joel via ntg-context wrote:
> I am creating a book that presents readers with a list of recommended
> materials.
> If materials are listed, then its displayed under the \subject{Materials}
> heading in a simple itemized list.
> I'm using \doifsomething{} to check if any items are listed.
Try \doiftext which typesets the material and checks its width.
> The problem I'm having is, when fed a blank macro, `\define\needsoven{}` it
> thinks there is content, so it displays the "Materials" heading, but an empty
> list. I have a custom macro that determins "if oven is needed" independent of
> these other items. So I need `\define\needsoven{}` to be regarded as nothing.
\define\needsoven makes \needsoven non-expandable. You either need
\defineexpandable\needsoven or use \doiftext
Aditya
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
[NTG-context] Is the Society of Biblical Literature (SBL) style files for ConTeXt incompatible with \setupinteraction[state=start]?
When I am using the SBL ConTeXt files for citations, if I add a line
`\setupinteraction[state=start` my code starts complaining:
Undefined control sequence \currentbtxloctext
\16>:btx:sbl:cite:inline
#1->\fastsetup {\s!btx :\s!cite :concat}\fastsetup
{btx:sbl:cite:lefttext}\begingroup \letbtxparameter {punct}\empty \def
\currentbtxcitealternative {inline}\def \currentbtxcategory {\btxfield
{category}}\def \currentbtxloctext
{\btxparameter {loctex
\normalexpanded
\Word {\fastsetup {btx:sbl:cite:inline}
}\doif {\btxparameter {righttext}}{\empty } {\btxperiod }
\strc_constructions_register_yes
...
Is this package incompatible with interaction?
--Joel
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
[NTG-context] Why does \doifsomething think there is content?
I am creating a book that presents readers with a list of recommended materials.
If materials are listed, then its displayed under the \subject{Materials}
heading in a simple itemized list.
I'm using \doifsomething{} to check if any items are listed.
The problem I'm having is, when fed a blank macro, `\define\needsoven{}` it
thinks there is content, so it displays the "Materials" heading, but an empty
list. I have a custom macro that determins "if oven is needed" independent of
these other items. So I need `\define\needsoven{}` to be regarded as nothing.
How can I get \doifsomething{} to think \define\needsoven{} is an empty value?
--Joel
My minimal working example is below:
\define\needsoven{}
\define[1]\materialsneeded{%
\doifsomething{#1}{
\subject{Materials}
\startitemize
#1
\stopitemize
}
}
\starttext
\chapter{Recipe 1}
\materialsneeded{\needsoven}
\subject{Instructions}
Spread peanut butter on sandwich.
\chapter{Recipe 2}
\materialsneeded{\item pizza cutter \item stove}
\subject{Instructions}
Preheat oven to 450 degrees F.
\stoptext
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
[NTG-context] Cron /var/www/aanhet.net/context/bin/cron/context-mirror
receiving incremental file list ./ ctan.lsr document-2.htm download-1.htm download-2.htm logo-ade.png logo-cts.png logo-pod.png rss.xml show-fil.pdf context/latest/ context/latest/cont-mpd.zip context/latest/cont-ppc.zip context/latest/cont-sci.zip context/latest/cont-tmf.zip context/latest/cont-tst.7z context/latest/cont-tst.tar.xz context/latest/cont-tst.zip sent 101,541 bytes received 20,926,823 bytes 3,823,338.91 bytes/sec total size is 449,311,457 speedup is 21.37 Running archiver: New dir: /var/www/aanhet.net/context//htdocs/archives/context-2023-01-15.15 122171514 /var/www/aanhet.net/context//htdocs/archives/context-2023-01-15.15/latest 126745317 /var/www/aanhet.net/context//htdocs/archives/context-2023-01-15.15/current 248920927 /var/www/aanhet.net/context//htdocs/archives/context-2023-01-15.15 248920927 total ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
