Ed is correct that algroup is not supported for Edit window display. Ideally, you should have different screen and print formatting, either in separate screen and print FOSIs, or in the same FOSI using specval and system-var. If your DTD is cooperative, suppress and savetext won't be needed, and the formatting in col1.fmt and col2.fmt can be coded directly in the first two e-i-cs.
For print/PDF output using FOSI, you need code along the lines of the following.
e-i-c gi=lang1-content-block
charlist inherit=1 charsubsetref=SUPPRESS
savetext textid=lang1-content-block.txt conrule=#CONTENT
...
e-i-c gi=lang2-content-block
charlist inherit=1 charsubsetref=SUPPRESS
savetext textid=lang2-content-block.txt conrule=#CONTENT
usetext placemnt=after source=<col1.fmt>,lang1-content-block.txt,</col1.fmt>
<col2.fmt>,lang2-content-block.txt,</col2.fmt>
...
e-i-c gi=col1.fmt
charlist inherit=1 charsubsetref=lang1-hyphenation
indent inherit=1leftind=0 firstln=* rightind=*+20pi
algroup refpoint=first
...
e-i-c gi=col2.fmt
charlist inherit=1 charsubsetref=lang2-hyphenation
indent inherit=1leftind=22pi firstln=* rightind=*+20pi
...
An e-i-c with algroup does not allow page breaks, so don't code algroup for col2.fmt. It is not necessary. Without algroup in col2.fmt,if col1 ends before col2 (col2 is deeper), a page break can occur in col2. If algroup is coded in both e-i-cs, then the whole structure is unbreakable. If it doesn't fit on the current page, it moves to the top of a new page. If the whole structure is deeper than a page, it oversets the page unless deepcontentsplitting is enabled.
It may be tempting to use gentables for this, buttables take longer to format than flowing text, and "deep" rows require the use of deepcontentsplitting.
Good luck!
Suzanne Napoleon
"WYSIWYG is last-century technology!"
www.FOSIexpert.com
