Solution NOT SOLVED Phantom Index Entries

2006-08-03 Thread Murray Moore
I can not delete the cause in the fm files that is the source of the phantom 
entries in my index, but I can hide the effect.

In my index I have made the offending index entries conditional and hidden them.

/\/\
Murray 
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.


Re: Solution NOT SOLVED Phantom Index Entries

2006-08-03 Thread Art Campbell

Why don't you think about getting IXGen from fsa.com and using it to
open all the markers. Then delete the problems...
http://www.fsatools.com/

Just in passing, it's a great indexing tool too, but that one
particular function would be useful to you in solving the problem.

Art



On 8/3/06, Murray Moore [EMAIL PROTECTED] wrote:

I can not delete the cause in the fm files that is the source of the phantom 
entries in my index, but I can hide the effect.

In my index I have made the offending index entries conditional and hidden them.





--
Art Campbell [EMAIL PROTECTED]
 ... In my opinion, there's nothing in this world beats a '52 Vincent
  and a redheaded girl. -- Richard Thompson
No disclaimers apply.
DoD 358
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]

or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.


RE: Solution NOT SOLVED Phantom Index Entries

2006-08-03 Thread Combs, Richard
Murray Moore wrote: 
 
 I can not delete the cause in the fm files that is the source 
 of the phantom entries in my index, but I can hide the effect.
 
 In my index I have made the offending index entries 
 conditional and hidden them.

I didn't really understand the initial problem, but whatever it was,
this isn't a solution -- or even an acceptable workaround. An index is a
generated file. When you update your book, your conditionalized entries
will be deleted and replaced with new, unconditionalized entries. 

To modify your index, you need to modify the index markers from which
it's generated, not the generated output. I don't recall why you weren't
able to find or edit the problematic marker text, but Art's suggestion
of getting IXGen is a good one. Use it to generate an editable marker
list, find and fix your problem entries in that list, and then reapply
the list to your doc, replacing all the existing markers. 

HTH!
Richard


--
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
--
rgcombs AT gmailDOTcom
303-777-0436
--




___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.


Re: Solution NOT SOLVED Phantom Index Entries

2006-08-03 Thread Frank Stearns


On Thu, 3 Aug 2006, Murray Moore wrote:


I can not delete the cause in the fm files that is the source of the


This is very peculiar... has to be an explanation somewhere! :)

Are you by chance pulling your files across a network? Perhaps stale or 
out-of-sync files are being moved around. (Many of the old network/FM 
problems of the past have been solved by better network sw in recent 
years, but one never knows when something might perhaps be out of 
adjustment or broken.)


If you'd like to send us a sample file I'll take a look at this B-grade 
SciFi/horror movie of the marker that won't go away. After nearly 2 
decades of working with MIF have never heard of anything like this (other 
than file sync issues). What you describe has gotten me rather curious.


If you elect to do this, send the original problematic binary file, not 
the MIF version you created.


Thanks,

Frank

Frank Stearns Associates | makers of IXgen(tm) for FrameMaker(r)
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
TOLL FREE Voice (USA and Canada):  800-567-6421
USA Voice: 360-892-3970  USA FAX: 360-253-1498
http://www.fsatools.com
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]

or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.


RE: Solution NOT SOLVED Phantom Index Entries

2006-08-03 Thread Murray Moore
My problem, Richard, is that I do not have a fm index marker to edit.

I call this entry in my book's index a ghost because its index marker text in 
Chapter 1 was changed a number of book index updates ago. The new version of 
that index entry displays in the index, too. When I look at that index marker 
in Chapter, I see only the revised text.

The older version of that index entry text only is found in the mif version of 
Chapter 1. When the free-of-the-ghost mif version is saved as the fm version 
and a stand-alone index is generated (thanks, Roger Shuttleworth), that ghost 
is gone.

But when the book then is updated, that ghost entry redisplays in my book's 
index. So the problem seems to occur during the updating of the 
book/regeneration of the index.

Whooo!

/\/\
Murray


-Original Message-
From: Combs, Richard [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 03, 2006 11:50 AM
To: Murray Moore; framers@lists.frameusers.com
Subject: RE: Solution NOT SOLVED Phantom Index Entries


Murray Moore wrote: 
 
 I can not delete the cause in the fm files that is the source 
 of the phantom entries in my index, but I can hide the effect.
 
 In my index I have made the offending index entries 
 conditional and hidden them.

I didn't really understand the initial problem, but whatever it was,
this isn't a solution -- or even an acceptable workaround. An index is a
generated file. When you update your book, your conditionalized entries
will be deleted and replaced with new, unconditionalized entries. 

To modify your index, you need to modify the index markers from which
it's generated, not the generated output. I don't recall why you weren't
able to find or edit the problematic marker text, but Art's suggestion
of getting IXGen is a good one. Use it to generate an editable marker
list, find and fix your problem entries in that list, and then reapply
the list to your doc, replacing all the existing markers. 

HTH!
Richard


--
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
--
rgcombs AT gmailDOTcom
303-777-0436
--
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.


Solution NOT SOLVED Phantom Index Entries

2006-08-03 Thread Murray Moore
I can not delete the cause in the fm files that is the source of the phantom 
entries in my index, but I can hide the effect.

In my index I have made the offending index entries conditional and hidden them.

/\/\
Murray 



Solution NOT SOLVED Phantom Index Entries

2006-08-03 Thread Art Campbell
Why don't you think about getting IXGen from fsa.com and using it to
open all the markers. Then delete the problems...
http://www.fsatools.com/

Just in passing, it's a great indexing tool too, but that one
particular function would be useful to you in solving the problem.

Art



On 8/3/06, Murray Moore  wrote:
> I can not delete the cause in the fm files that is the source of the phantom 
> entries in my index, but I can hide the effect.
>
> In my index I have made the offending index entries conditional and hidden 
> them.
>



-- 
Art Campbell art.campbell at 
gmail.com
  "... In my opinion, there's nothing in this world beats a '52 Vincent
   and a redheaded girl." -- Richard Thompson
 No disclaimers apply.
 DoD 358



Solution NOT SOLVED Phantom Index Entries

2006-08-03 Thread Combs, Richard
Murray Moore wrote: 

> I can not delete the cause in the fm files that is the source 
> of the phantom entries in my index, but I can hide the effect.
> 
> In my index I have made the offending index entries 
> conditional and hidden them.

I didn't really understand the initial problem, but whatever it was,
this isn't a solution -- or even an acceptable workaround. An index is a
generated file. When you update your book, your conditionalized entries
will be deleted and replaced with new, unconditionalized entries. 

To modify your index, you need to modify the index markers from which
it's generated, not the generated output. I don't recall why you weren't
able to find or edit the problematic marker text, but Art's suggestion
of getting IXGen is a good one. Use it to generate an editable marker
list, find and fix your problem entries in that list, and then reapply
the list to your doc, replacing all the existing markers. 

HTH!
Richard


--
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
--
rgcombs AT gmailDOTcom
303-777-0436
--







Solution NOT SOLVED Phantom Index Entries

2006-08-03 Thread Frank Stearns

On Thu, 3 Aug 2006, Murray Moore wrote:

> I can not delete the cause in the fm files that is the source of the

This is very peculiar... has to be an explanation somewhere! :)

Are you by chance pulling your files across a network? Perhaps stale or 
out-of-sync files are being moved around. (Many of the old network/FM 
problems of the past have been solved by better network sw in recent 
years, but one never knows when something might perhaps be out of 
adjustment or broken.)

If you'd like to send us a sample file I'll take a look at this B-grade 
SciFi/horror movie of the marker that won't go away. After nearly 2 
decades of working with MIF have never heard of anything like this (other 
than file sync issues). What you describe has gotten me rather curious.

If you elect to do this, send the original problematic binary file, not 
the MIF version you created.

Thanks,

Frank

Frank Stearns Associates | makers of IXgen(tm) for FrameMaker(r)
franks at fsatools.com 
TOLL FREE Voice (USA and Canada):  800-567-6421
USA Voice: 360-892-3970  USA FAX: 360-253-1498
http://www.fsatools.com