--- "Lynne A. Price" <[EMAIL PROTECTED]> wrote:
Thank you Lynne for confirming that this bug has been
propagated through all releases of structured
FrameMaker.
==
> 1) You comment that it doesn't matter whether the
> text range is defined as
> an inclusion or c
--- "Lynne A. Price" wrote:
Thank you Lynne for confirming that this bug has been
propagated through all releases of structured
FrameMaker.
==
> 1) You comment that it doesn't matter whether the
> text range is defined as
> an inclusion or contextual element.
At 07:21 AM 3/31/2006, Daniel Emory wrote:
This bug is in FM+SGML 6, and I'm curious whether it's
also in later releases.
...The bug is unaffected by whether
the Footnote element is included in the structure rule
of those text containers, or is listed as an inclusion
under those text containers.
At 07:21 AM 3/31/2006, Daniel Emory wrote:
>This bug is in FM+SGML 6, and I'm curious whether it's
>also in later releases.
>
>...The bug is unaffected by whether
>the Footnote element is included in the structure rule
>of those text containers, or is listed as an inclusion
>under those text contai
This bug is in FM+SGML 6, and I'm curious whether it's
also in later releases.
I have an EDD in which an element of type Footnote
(not surprisingly, the element name is also Footnote)
is provided for most elements that have in
their structure rule. The bug is unaffected by whether
the Footnote el
This bug is in FM+SGML 6, and I'm curious whether it's
also in later releases.
I have an EDD in which an element of type Footnote
(not surprisingly, the element name is also Footnote)
is provided for most elements that have in
their structure rule. The bug is unaffected by whether
the Footnote el