Johan, I just experienced this bug with one of my chapters too. It was the
first time I'd worked with this particular book. One of the chapters has dozens
of xrefs that are within conditional text that is hidden, so I get dozens of
broken xref messages when I generate. With my books, if I use
That's good to hear. Unfortunately, in our case, the xrefs are seldom
broken, because they lead to other texts that are indeed present in the
book, but hidden from view. So instead I will get texts in my files like:
To avoid this behavior, include the optional header file.page134
where
This happened to me once.
Was a pretty weird experience and I am sure it was something easily
fixed. I looked into the reference pages and there did not appear to
be anything untoward. I think it occurred because I used the chapters
sequentially as templates for subsequent chapters but I
That's good to hear. Unfortunately, in our case, the xrefs are seldom
broken, because they lead to other texts that are indeed present in the
book, but hidden from view. So instead I will get texts in my files like:
"To avoid this behavior, include the optional header file.page134"
where
t part --
An HTML attachment was scrubbed...
URL:
<http://lists.frameusers.com/pipermail/framers/attachments/20111013/26e5946b/attachment.html>
