From: Andreas Harder <andreas.harder@rz-online.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bugs in current beta
Date: Wed, 11 Aug 2010 11:31:19 +0200 [thread overview]
Message-ID: <6DA3ECC0-171C-49D0-B328-C5241593B277@rz-online.de> (raw)
In-Reply-To: <4C626BBA.5050307@wxs.nl>
Am 11.08.2010 um 11:22 schrieb Hans Hagen:
> On 10-8-2010 5:36, Andreas Harder wrote:
>> Hi all,
>>
>> for me (OS X 10.6.4)
>> mtxrun –script server –auto
>> do not work. If I click on a font name I get:
>> MTXrun | request from: 127.0.0.1
>> MTXrun | requested action: /mtx-server-ctx-fonttest.lua?selection=hoeflertextregular
>> MTXrun | performing action: /mtx-server-ctx-fonttest.lua?selection=hoeflertextregular
>> MTXrun | requested file '/mtx-server-ctx-fonttest.lua?selection=hoeflertextregular'
>> MTXrun | handling error 404: Not Found
>>
>> Another thing is the streams-module. Here is an example:
>>
>> \usemodule[streams]
>> \definestreamlayer[test][method=overlay]
>> \setupbackgrounds[page][background=test]
>>
>> \starttext \showframe
>> \startstreamlayer[test]
>> \startcolumns
>> \input knuth
>> \stopcolumns
>> \stopstreamlayer
>>
>> \setlayer[test][x=5cm,y=10cm]{\placestreamlayer[test]}
>> \stoptext
>>
>> And here the error:
>> ! Undefined control sequence.
>> l.19 \defineoutputstream[\v!left]
>
> This is not really a bug. Streams in mkii are an experiment and will not be developed further (is a module after all). In mkiv there will be a different mechanism. There is some experimental code ... copied from the source:
>
> \enabletrackers[streams.flushing]
>
> \setuplayout[grid=yes] \showgrid
>
> \starttext
>
> \input tufte
>
> \startoutputstream[nl]
>
> Wat doen we hier?
>
> \enableoutputstream[en]
>
> Are you sleeping, brother John?\footnote{xxx}
>
> \dorecurse{4}{x \footnote{note \recurselevel}\input tufte \par \pushoutputstream}
>
> \enableoutputstream[de]
>
> Bruder Jakob, schläfst du noch?\footnote{yyy}
>
> \dorecurse{4}{x \footnote{note \recurselevel}\input ward \par \pushoutputstream}
>
> \disableoutputstream
>
> \stopoutputstream
>
> Vader Jacob, slaap je nog?\footnote{zzz}
>
> \input tufte
>
> \synchronizestreams[en,de,nl]
>
> \page \flushoutputstream[en] \input knuth
> \page \flushoutputstream[de] \input knuth
> \page \flushoutputstream[nl] \input knuth
>
> \stoptext
>
> Hans
Hello Hans,
big thanks for the explanation.
Andreas
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-08-11 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 15:36 Andreas Harder
2010-08-10 21:44 ` Andreas Harder
2010-08-11 8:08 ` Hans Hagen
2010-08-11 9:22 ` Hans Hagen
2010-08-11 9:31 ` Andreas Harder [this message]
2010-08-13 11:59 ` Bugs in current beta (streams) Salil Sayed
2010-08-16 23:50 ` Hans Hagen
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=6DA3ECC0-171C-49D0-B328-C5241593B277@rz-online.de \
--to=andreas.harder@rz-online.de \
--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).