Once a writer had the reviewer's final sign-off for a chapter, the XyWrite files were passed to the BestInfo group, where a composition specialist would lay out the pages.
Like XyWrite, BestInfo stores its files as ASCII text, but because its codes are more complicated, the conversion from XyWrite to BestInfo cannot be automated fully, so laying out the pages in BestInfo is a manual task.
Instead, they saw simple printouts from the XyWrite files.
Writers made the changes to the XyWrite files and put them through BestInfo all over again, or
Composition specialists made the changes to the BestInfo files, with the writers maybe remembering to add them to the XyWrite files later.
By the end of most projects, the text in the XyWrite files and the text in the BestInfo files didn't match.
I was assigned the job of setting up XyWrite in a way that would make it easier for the technical writers to learn.
We immediately realized that, if technical writers used raw XyWrite formatting codes, every file would be a custom document.
Like most word processors, XyWrite lets you define styles and use them to format text.
It was the undocumented BI = 1 setting that allowed us to use these tags in our XyWrite files.
With it, technical writers were productively using XyWrite in just two or three days.