Article View: adobe.framemaker
Article #25277Re: Adding numeric index markers
From: Sheila Carlisle
Date: Sun, 14 Jul 2002 18:25
Date: Sun, 14 Jul 2002 18:25
7 lines
1617 bytes
1617 bytes
If a) you wanted to get into MIF coding, and b) your parts book source was coming from some sort of a database or text file that you could manipulate, or even c) if you can save your existing FM tables out as text, then you could automate the creation of the index markers quite easily, Mike. Even by using something like an Excel spreadsheet you can add the index markers and make a MIF file with a table that will open just fine in FM, then you can replace the existing table with the newly created table w/markers. I have a very old example file showing this kind of a process for markers and tables. If anybody would like to see it, beam me an e-mail ( scarlisle at axialinfo dot com ) and I'd be happy to send it along. The key files are all just text files, so you don't need any special app. to view them. [PLEASE be sure to specify it's the MIF-markers example file you'd like to see] Sheila
Technical Details
Message-ID:
<ef99ef2.0@WebX.aaQKaf7vad4>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-01!sn-xit-08!supernews.com!newsfeed.news2me.com!proxad.net!gatel-ffm!newsfeed01.sul.t-online.de!t-online.de!WebXReferences:
<ef99ef2.-1@WebX.aaQKaf7vad4>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fd315,9c71d94048174fbb X-Google-Attributes: gidfd315,public X-Google-ArrivalTime: 2002-07-14 11:41:39 PST From: "Sheila Carlisle" <scarlisle@axialinfo.com> Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-01!sn-xit-08!supernews.com!newsfeed.news2me.com!proxad.net!gatel-ffm!newsfeed01.sul.t-online.de!t-online.de!WebX Newsgroups: adobe.framemaker Subject: Re: Adding numeric index markers Message-ID: <ef99ef2.0@WebX.aaQKaf7vad4> Date: Sun, 14 Jul 2002 11:25:26 -0700 References: <ef99ef2.-1@WebX.aaQKaf7vad4> Lines: 19 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit