Marsha,
There is nothing bad about old workhorses...
* What are the names of the ID attributes in your title or sections
elements and what is the name of the IDREF attribute in your
CrtossReference element?
* There is no easy migration from WWP8.x to Webworks ePublisher!
* You should upgrade
Marsha,
There is nothing bad about old workhorses...
* What are the names of the ID attributes in your title or sections
elements and what is the name of the IDREF attribute in your
CrtossReference element?
* There is no easy migration from WWP8.x to Webworks ePublisher!
* You should upgrade
am using 8.0.0.1194
with which the xrefs still work, but not with FM 7.2. I have to keep 7.1
installed to use it.
Russ
--
Message: 24
Date: Wed, 28 Feb 2007 13:11:15 -0800
From: Jeremy H. Griffith [EMAIL PROTECTED]
Subject: Re: Cross Refs, Structured FM, and WWP
One other way to fix this is to use FrameScript or an API client to
temporarily convert the cross-references into spot cross-references. This
involves inserting a Cross-Ref marker at the source and setting its text to
the unique id. Then the cross-reference properties are changed so that the
On Thu, 1 Mar 2007 08:13:55 -0500, Rick Quatro [EMAIL PROTECTED]
wrote:
One other way to fix this is to use FrameScript or an API client to
temporarily convert the cross-references into spot cross-references. This
involves inserting a Cross-Ref marker at the source and setting its text to
the
Hi Jeremy,
Your points are valid, but I generally do this on a copy of the book before
it is processed by WWP. The markers and modified cross-references are in the
throw-away documents for the conversion process, not in the documents that
are maintained going forward.
Rick
Interesting,
am using 8.0.0.1194
with which the xrefs still work, but not with FM 7.2. I have to keep 7.1
installed to use it.
Russ
--
Message: 24
Date: Wed, 28 Feb 2007 13:11:15 -0800
From: "Jeremy H. Griffith" <jer...@omsys.com>
Subject: Re: Cross Ref
One other way to fix this is to use FrameScript or an API client to
temporarily convert the cross-references into spot cross-references. This
involves inserting a Cross-Ref marker at the source and setting its text to
the unique id. Then the cross-reference properties are changed so that the
On Thu, 1 Mar 2007 08:13:55 -0500, "Rick Quatro"
wrote:
>One other way to fix this is to use FrameScript or an API client to
>temporarily convert the cross-references into spot cross-references. This
>involves inserting a Cross-Ref marker at the source and setting its text to
>the unique id.
Hi Jeremy,
Your points are valid, but I generally do this on a copy of the book before
it is processed by WWP. The markers and modified cross-references are in the
"throw-away documents" for the conversion process, not in the documents that
are maintained going forward.
Rick
> Interesting,
FM 7.2b128 - Structured
WWP 8.6.6587.0 (Yes, I know it is old.)
I sent the following query to the WebWorks list but got no replies. I'm
hoping someone here can help...
After searching through the WWP list archives, I notice that cross
references were not (are not?) working with structured
FM 7.2b128 - Structured
WWP 8.6.6587.0 (Yes, I know it is old.)
I sent the following query to the WebWorks list but got no replies. I'm
hoping someone here can help...
After searching through the WWP list archives, I notice that cross
references were not (are not?) working with structured
On Wed, 28 Feb 2007 11:35:28 -0500, "Lofthouse Marsha-PT1816"
wrote:
>FM 7.2b128 - Structured
>WWP 8.6.6587.0 (Yes, I know it is old.)
>
>I sent the following query to the WebWorks list but got no replies. I'm
>hoping someone here can help...
>
>After searching through the WWP list archives, I
13 matches
Mail list logo
