ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Hamid,Idris" <Idris.Hamid@ColoState.EDU>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: streams reversed?
Date: Fri, 15 Sep 2023 12:43:22 +0000	[thread overview]
Message-ID: <em20d2f19c-958c-49b5-8083-bc61fa295ef4@b8976724.com> (raw)
In-Reply-To: <123ce5aa-0795-e35a-ab59-9a480af86525@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 4025 bytes --]

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<mailto:roma83537@gmail.com>>
To "Bruce Horrocks" <ntg@scorecrow.com<mailto:ntg@scorecrow.com>>; "mailing list for ConTeXt users" <ntg-context@ntg.nl<mailto: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<mailto: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

[-- Attachment #1.2: Type: text/html, Size: 8205 bytes --]

[-- Attachment #2: Type: text/plain, Size: 495 bytes --]

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

  reply	other threads:[~2023-09-15 12:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13  6:47 [NTG-context] " jbf
2023-09-14 10:14 ` [NTG-context] " Bruce Horrocks
2023-09-14 22:04   ` jbf
2023-09-15 12:43     ` Hamid,Idris [this message]
2023-09-15 22:57       ` jbf
2023-09-17  8:01         ` Hans Hagen via ntg-context
     [not found]     ` <611158B6-83A3-424A-823C-78CA3C3EAFAD@scorecrow.com>
2023-09-15 22:55       ` jbf

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=em20d2f19c-958c-49b5-8083-bc61fa295ef4@b8976724.com \
    --to=idris.hamid@colostate.edu \
    --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).