🚀 go-pugleaf

I'm afraid I spoke too soon. The garbage is for something else. It occurs in
our template (something on the reference page).

I did more searching in the MIF file and found that the writer had
apparently changed the file name for some of the inset files. (She failed to
mention that to me, of course.) The MIF entry was as follows:

    <TiSrcFile `<c\>TextInsets<c\>UDFCardforCTDAA.fm'>

When I checked her file folder, however, the actual file name was
UDFCardforCTDAAandFields.fm. When I added "andFields" to the file name in
the MIF entry, that inset (and others like it) worked fine.

I think the problem for the last one was that she moved the inset to a
different folder. The MIF entry for that inset was <TiSrcFile
`<u\><c\>9XXCards<c\>TextInsets<c\>UDFCardforCTDARandFields.fm'> in one
location and <TiSrcFile `<c\>TextInsets<c\>UDFCardforCTDARandFields.fm'> in
another. (The inset contains two different flows that she referenced
separately.) When I changed the path so that they matched, the inset worked
fine.

Apparently, this problem will fix itself once I can convince my writer to
stop changing things!!!

Thanks anyway, Thomas.

Rick