🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: adobe.framemaker
Article #23603

Re: Fixing the pgfid-#### tags in files?

#23603
From: Simon BUCH
Date: Fri, 22 Nov 2002 17:09
28 lines
2995 bytes
I have seen this behaviour before when a document is reused within a book file. This may occur if you make use of a source template document where only paragraph content changes. 

FrameMaker creates unique paragraph ID numbers when new paragraphs are created. However, if you create a new document using a template document and simply change only the paragraph content, the paragraph ID numbers do not change. If you then add these files are to a FrameMaker book, the situation can occur where there are 2 paragraphs with the same ID number. 

FrameMaker generates HTML with named anchor tags based on a the ''<Unique'' ID number of paragraphs, which then means you could have duplicate tags. As a result of this, clicking on a HTML hypertext link may not take you to the correct place. For example, in Internet Explorer or OmniWeb, clicking on a HTML link will take you to the first occurrence of the named anchor tag, whereas Netscape Navigator, will take you to the last occurance. 

There's 2 potential ways to fix this. 
#1 - Ensure that all paragraphs have unique ID numbers by editing the structure of the documents 
1.1 Save each FrameMaker document as Maker Interchange Format (MIF). 
1.2 using a text editor, remove any occurance of ''<Unique '' MIF statements. 
1.3 Open each MIF file and save as a FrameMaker document. 
1.4 Export to HTML. 
(Unix users can easily automate this process by using FrameMaker's FMbatch utility with shell scripts and text processing tools) 

#2 - Ensure that all paragraphs have unique ID numbers by forcing new paragraph ID's. 
2.1 Select all of the text flow (!ea) 
2.2 Cut out all of the text flow (!ex) 
2.3 Use File->SaveAs and overwrite the existing file (!fa) 
2.4 Paste the contents of the clipboard (!ep) 
2.5 Save the document as FrameMaker format. 
2.6 Export to HTML. 

#1 above works by way of forcing FrameMaker to assign new ID numbers. This works best if you round-trip (FM to MIF and back to FM format) ALL your documents. 

#2 works ONLY is you select File->SaveAs, as FrameMaker will tidy up the internal structure of a document and expunge any unused items, and when the paragraphs are pasted back in the document, new paragraph ID numbers are generated. 

I hope this helps. 
Let us know if it works!
Technical Details
Message-ID: <1de6b648.3@WebX.la2eafNXanI>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-03!sn-xit-01!sn-xit-04!supernews.com!news.maxwell.syr.edu!nntp.infostrada.it!newsfeed01.sul.t-online.de!t-online.de!WebX
References: <1de6b648.-1@WebX.la2eafNXanI>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fd315,3e33017a64d804a7
X-Google-Attributes: gidfd315,public
X-Google-ArrivalTime: 2002-11-22 09:38:05 PST
From: "Simon BUCH" <simon.buch@adobe.com>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-03!sn-xit-01!sn-xit-04!supernews.com!news.maxwell.syr.edu!nntp.infostrada.it!newsfeed01.sul.t-online.de!t-online.de!WebX
Newsgroups: adobe.framemaker
Subject: Re: Fixing the pgfid-#### tags in files?
Message-ID: <1de6b648.3@WebX.la2eafNXanI>
Date: Fri, 22 Nov 2002 09:09:44 -0800
References: <1de6b648.-1@WebX.la2eafNXanI>
Lines: 50
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit