From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, URIBL_SBL_A autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 16664 invoked from network); 15 Sep 2023 23:01:35 -0000 Received: from cgl.ntg.nl (5.39.185.202) by inbox.vuxu.org with ESMTPUTF8; 15 Sep 2023 23:01:35 -0000 Received: from localhost (localhost [127.0.0.1]) by cgl.ntg.nl (Postfix) with ESMTP id 55034482F2C for ; Sat, 16 Sep 2023 01:00:52 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at cgl.ntg.nl Received: from cgl.ntg.nl ([127.0.0.1]) by localhost (cgl.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RWCmBt76ClDn for ; Sat, 16 Sep 2023 01:00:51 +0200 (CEST) Received: from cgl.ntg.nl (localhost [127.0.0.1]) by cgl.ntg.nl (Postfix) with ESMTP id E445F4830F0 for ; Sat, 16 Sep 2023 00:59:36 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by cgl.ntg.nl (Postfix) with ESMTP id E1F0E4830C9 for ; Sat, 16 Sep 2023 00:59:19 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at cgl.ntg.nl Received: from cgl.ntg.nl ([127.0.0.1]) by localhost (cgl.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vjdRA3p70pgE for ; Sat, 16 Sep 2023 00:59:19 +0200 (CEST) Received: from mail-pj1-f44.google.com (mail-pj1-f44.google.com [209.85.216.44]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by cgl.ntg.nl (Postfix) with ESMTPS id C7146482FF5 for ; Sat, 16 Sep 2023 00:57:15 +0200 (CEST) Received: by mail-pj1-f44.google.com with SMTP id 98e67ed59e1d1-274972a4cb6so1043287a91.1 for ; Fri, 15 Sep 2023 15:57:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1694818634; x=1695423434; darn=ntg.nl; h=in-reply-to:from:cc:references:to:content-language:subject :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=Rxfad975ufMORI6zxaUUGETPn2Pbk3rI25WOrBSYGyg=; b=MPnoHqoFHwjVm8hXO6Jm7H2xyjJ4k5P42LMugtKjUhhTvTUSxSPbOvX02OxhgFSTCE 2hZ33KkPi3e8/97IWnv7bb/la4zl+KZp9DK/lG3pQjCqHu0IszDGYCmuyzstXuvKQCFe bvtj0KEwXApiPCDaiu0GbMElE/w981si5Mq0jwpg4CvU+F11VODuEbr5jObEyDPGfFbw BShIJB9QpXkgEiSijj8AoLCBVrcQdQdypoUWe2/foTBpqKyGcVpJqtFaeNr+7sJXObGp gDEyciK2NM/TkAfwG7mVK9PEOg2hnqR5VrniRSh29G6QZ8G3Jae5o5p7/AbP//+B2B/5 OV0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694818634; x=1695423434; h=in-reply-to:from:cc:references:to:content-language:subject :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=Rxfad975ufMORI6zxaUUGETPn2Pbk3rI25WOrBSYGyg=; b=TPyC6N6WqL4eYv6YwEi6NmUHFECLLZK+DFFxcB3PeifNbpyaT5Lvk4fIaB5k/kIBYg zg4Lrk8doVMODPzHocpZWTUfb+vCP3nbgrV0NVlMramACbM9Z4S4oWwzXd/Upq4qgmRc ri9jOOS9NYijOMdp2BS05tjcySDqx3DJQO/t6zq3PBayYKIiIAYr8AyjM3Y7QNLZ/qpr jAxVv33Hexa1n2ymqtTJCi/nj5morRWjCxRiergSGoCsSWWVcxWJLohUmjhT6O6mPJu3 2T+WNx2kMnUA0JyUtO5ek4Gg7kmopy83P/FrHEV1qkXUI0zv4YrEWekSxMDiN3/rGRaW /gEg== X-Gm-Message-State: AOJu0YwOLs6Dc0k+Migy4UdY7DHqjwZ4WjhxZ9QWm9qf/+fN0S4vwSNk yqwO4Yzflx5YeEVAvLFsQb8= X-Google-Smtp-Source: AGHT+IEpqYbI15RGUEHfh9/pcukzALGaXYS85U/R4wwYWvUIkTY0BcMUxarRg6wGPgUt24JwV6w6ng== X-Received: by 2002:a17:90a:43c2:b0:26b:48e8:cd76 with SMTP id r60-20020a17090a43c200b0026b48e8cd76mr2923441pjg.37.1694818634047; Fri, 15 Sep 2023 15:57:14 -0700 (PDT) Received: from [192.168.1.5] ([101.115.128.167]) by smtp.gmail.com with ESMTPSA id ge13-20020a17090b0e0d00b00256799877ffsm103590pjb.47.2023.09.15.15.57.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 15 Sep 2023 15:57:13 -0700 (PDT) Message-ID: <51db6432-72c4-da23-620e-fda4d745b774@gmail.com> Date: Sat, 16 Sep 2023 08:57:08 +1000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Content-Language: en-AU To: "Hamid,Idris" References: <20f6346e-2e52-f65b-e716-fd281285e070@gmail.com> <123ce5aa-0795-e35a-ab59-9a480af86525@gmail.com> From: jbf In-Reply-To: Message-ID-Hash: R5CBDGARCEAA2QLMAOYGUI3VWL5M64GB X-Message-ID-Hash: R5CBDGARCEAA2QLMAOYGUI3VWL5M64GB X-MailFrom: roma83537@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: mailing list for ConTeXt users X-Mailman-Version: 3.3.8 Precedence: list Reply-To: mailing list for ConTeXt users Subject: [NTG-context] Re: streams reversed? List-Id: mailing list for ConTeXt users Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: multipart/mixed; boundary="===============3976310040779748182==" This is a multi-part message in MIME format. --===============3976310040779748182== Content-Type: multipart/alternative; boundary="------------3JBdYa3U5vALaqoyOWlkmIKR" Content-Language: en-AU This is a multi-part message in MIME format. --------------3JBdYa3U5vALaqoyOWlkmIKR Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Thanks Idris. See my response to Bruce, and indeed his response to mine earlier. I'll have to leave it at that for now. Too many other matters pressing. Julian On 15/9/23 22:43, Hamid,Idris wrote: > Hi Julian, > > Am also interested in this matter (and played a bit with the code you > provided); one suspects that others are as well. > > Based on past experience, can affirm that it's sometimes > time-consuming, even a pain, to produce an MWE to reproduce the > relevant behavior. But it would be well worth the effort for the sake > of improving the streams mechanism and clarifying its ultimate > limitations. > > Even if the final MWE seems too bulky, you could post cloud links to > the source and pdf files. Thank you for your contribution. > > Best wishes > Idris > > ------ Original Message ------ > From "jbf" > To "Bruce Horrocks" ; "mailing list for ConTeXt > users" > Date 9/14/2023 4:04:27 PM > Subject [NTG-context] Re: streams reversed? > >> ** Caution: EXTERNAL Sender ** >> Bruce, that was kind of you to reply. I think we both know that the >> streams mechanism, while 'workable' for the most part, is still in need >> of refinement. >> It is quite possible that what is causing my problem has less to do with >> 'streams' per se, and more to do with the use of this mechanism in a >> 'real book' using frontmatter, bodymatter etc. etc. >> Since it would be too long and complicated an MWE to place here in the >> list to demonstrate my problem, I will send you the file separately so >> you can see the issue: effectively, the streams have worked for >> frontmatter (Foreword), but when I get to Chapter 1 in bodymatter, they >> are reversed. You will see that. I can't work out why, but you might be >> able to see what is causing that. >> And of course, I have two other problems to work out before I could use >> this in a real production scenario: there is the one you have already >> alluded to of extra pages occasionally beforehand (hopefully easily >> solvable) but I can see another problem when the text is a lengthy >> one... and this is the result of synchronization: when one language (vi) >> takes up more space than the other (en), we get an awkward break at the >> end of the chapter in en, so that the last line can 'catch up' with the >> last paragraph (in vi). Maybe this one will be harder to solve! >> Julian >> On 14/9/23 20:14, Bruce Horrocks wrote: >>> On 13 Sep 2023, at 07:47, jbf wrote: >>>> When I come to bodymatter and Chapter 1, again it works, except >>>> that the positions of the languages are reversed, so I end up with >>>> vi on the left and en on the right. By Chapter 2 we are back to the >>>> correct position once more (en left and vi right). >>>> I want to know why this is happening, and if I can prevent it >>>> happening. >>> I've modified the sample code you got from Wolfgang to include >>> chapter headings and it all looks fine to me[1] - the red text is >>> all on the right hand side and the greeen text is all on the left. >>> If this doesn't help and you still have problems then you'll need to >>> post a sample that actually shows the problem. I'm using ConTeXt >>> ver: 2023.09.04 19:15. >>> \starttext >>> \startoutputstream[one] >>> \startcolor[red] >>> \dorecurse{5}{\chapter{Stream One} >>> \dorecurse{10}{\input knuth\par} >>> } >>> \stopcolor >>> \stopoutputstream >>> \startoutputstream[two] >>> \startcolor[green] >>> \dorecurse{5}{\chapter{Stream Two} >>> \dorecurse{10}{\input zapf\par} >>> } >>> \stopcolor >>> \stopoutputstream >>> \synchronizestreams[one,two] >>> \setbox\scratchboxone\outputstreambox[one] >>> \setbox\scratchboxtwo\outputstreambox[two] >>> \doloop >>> {\ifvoid\scratchboxone >>> \exitloop >>> \else >>> \setbox\scratchboxfour\vsplit\scratchboxone to \textheight >>> \vbox to \vsize{\box\scratchboxfour\vss}% >>> \setbox\scratchboxfive\vsplit\scratchboxtwo to \textheight >>> \vbox to \vsize{\box\scratchboxfive\vss}% >>> \fi} >>> \stoptext >>> [1] Apart from unnecessary blank pages at the beginning but that's a >>> different problem so I'm not addressing that for now. >>> — >>> Bruce Horrocks > -- > Idris Samawi Hamid, Professor > Department of Philosophy > Colorado State University > Fort Collins, CO 80523 --------------3JBdYa3U5vALaqoyOWlkmIKR Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

Thanks Idris.

See my response to Bruce, and indeed his response to mine earlier. I'll have to leave it at that for now. Too many other matters pressing.

Julian

On 15/9/23 22:43, Hamid,Idris wrote:
Hi Julian,

Am also interested in this matter (and played a bit with the code you provided); one suspects that others are as well. 

Based on past experience, can affirm that it's sometimes time-consuming, even a pain, to produce an MWE to reproduce the relevant behavior. But it would be well worth the effort for the sake of improving the streams mechanism and clarifying its ultimate limitations.

Even if the final MWE seems too bulky, you could post cloud links to the source and pdf files. Thank you for your contribution.

Best wishes
Idris

------ Original Message ------
From "jbf" <roma83537@gmail.com>
To "Bruce Horrocks" <ntg@scorecrow.com>; "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Date 9/14/2023 4:04:27 PM
Subject [NTG-context] Re: streams reversed?

** Caution: EXTERNAL Sender **
 
Bruce, that was kind of you to reply. I think we both know that the
streams mechanism, while 'workable' for the most part, is still in need
of refinement.
 
It is quite possible that what is causing my problem has less to do with
'streams' per se, and more to do with the use of this mechanism in a
'real book' using frontmatter, bodymatter etc. etc.
 
Since it would be too long and complicated an MWE to place here in the
list to demonstrate my problem, I will send you the file separately so
you can see the issue: effectively, the streams have worked for
frontmatter (Foreword), but when I get to Chapter 1 in bodymatter, they
are reversed. You will see that. I can't work out why, but you might be
able to see what is causing that.
 
And of course, I have two other problems to work out before I could use
this in a real production scenario: there is the one you have already
alluded to of extra pages occasionally beforehand (hopefully easily
solvable) but I can see another problem when the text is a lengthy
one... and this is the result of synchronization: when one language (vi)
takes up more space than the other (en), we get an awkward break at the
end of the chapter in en, so that the last line can 'catch up' with the
last paragraph (in vi). Maybe this one will be harder to solve!
 
Julian
 
On 14/9/23 20:14, Bruce Horrocks wrote:
On 13 Sep 2023, at 07:47, jbf <roma83537@gmail.com> wrote:
When I come to bodymatter and Chapter 1, again it works, except that the positions of the languages are reversed, so I end up with vi on the left and en on the right. By Chapter 2 we are back to the correct position once more (en left and vi right).
I want to know why this is happening, and if I can prevent it happening.
 
I've modified the sample code you got from Wolfgang to include chapter headings and it all looks fine to me[1] - the red text is all on the right hand side and the greeen text is all on the left. If this doesn't help and you still have problems then you'll need to post a sample that actually shows the problem. I'm using ConTeXt ver: 2023.09.04 19:15.
 
\starttext
 
\startoutputstream[one]
\startcolor[red]
\dorecurse{5}{\chapter{Stream One}
\dorecurse{10}{\input knuth\par}
}
\stopcolor
\stopoutputstream
 
\startoutputstream[two]
\startcolor[green]
\dorecurse{5}{\chapter{Stream Two}
\dorecurse{10}{\input zapf\par}
}
\stopcolor
\stopoutputstream
 
\synchronizestreams[one,two]
 
\setbox\scratchboxone\outputstreambox[one]
\setbox\scratchboxtwo\outputstreambox[two]
 
\doloop
{\ifvoid\scratchboxone
\exitloop
\else
\setbox\scratchboxfour\vsplit\scratchboxone to \textheight
\vbox to \vsize{\box\scratchboxfour\vss}%
\setbox\scratchboxfive\vsplit\scratchboxtwo to \textheight
\vbox to \vsize{\box\scratchboxfive\vss}%
\fi}
 
\stoptext
 
 
[1] Apart from unnecessary blank pages at the beginning but that's a different problem so I'm not addressing that for now.
 
—
Bruce Horrocks
--
Idris Samawi Hamid, Professor
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
--------------3JBdYa3U5vALaqoyOWlkmIKR-- --===============3976310040779748182== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___________________________________________________________________________________ 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 ___________________________________________________________________________________ --===============3976310040779748182==--