ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Streams
Date: Wed, 23 Nov 2011 20:43:18 +0100	[thread overview]
Message-ID: <FCB42970-7295-44D1-91BB-D25A3C1F4D09@googlemail.com> (raw)
In-Reply-To: <9A88839D-DB8D-458D-9C3B-8ECD688A7BB4@boede.nl>


Am 23.11.2011 um 20:31 schrieb Willi Egger:

> Hi,
> 
> I was looking for a possibility to typeset an article left in the original language and right in the translation.I found then the mail of Thomas, when he announced the availability of streams (2006). - Great, that is what I am looking for!
> 
> However when issuing \usemodule[streams] I get immediately a fatal error: undefined controlsequence. I believe is \defineoutputstream. 
> 
> So it looks like the module is broken. - Is there another approach to get two texts in different languages next to each other?

You don’t need the mode for MkIV. Below is a example 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

Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2011-11-23 19:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 19:31 Streams Willi Egger
2011-11-23 19:43 ` Wolfgang Schuster [this message]
2011-11-23 22:09   ` Streams Willi Egger
  -- strict thread matches above, loose matches on Subject: below --
2010-03-11 10:47 streams Philipp Gesang
2010-03-11 18:37 ` streams Hans Hagen
2010-03-12 22:43   ` streams Philipp Gesang
2010-03-13 12:20     ` streams Hans Hagen
2008-04-11  9:45 Streams Roman Sigg
2008-04-11 20:05 ` Streams Henning Hraban Ramm
2008-04-12  5:08 ` Streams Bert Trüger
2008-04-12 22:02 ` Streams luigi scarso
2008-04-13 18:28   ` Streams Henning Hraban Ramm
2007-03-07 19:43 Streams Idris Samawi Hamid

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=FCB42970-7295-44D1-91BB-D25A3C1F4D09@googlemail.com \
    --to=schuster.wolfgang@googlemail.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).