Re: Large FM File

2008-05-02 Thread Whites
% matches can be very high. But I guess it is a better idea to stop changing file names and moving around text than merging all FM files into one. ;-) /Åsa -- Message: 5 Date: Thu, 1 May 2008 14:32:50 -0400 From: Neil Tubb [EMAIL PROTECTED] Subject: Large FM File

RE: Large FM File

2008-05-02 Thread poshedly
Tubb Subject: Large FM File To: Message-ID: Content-Type: text/plain; charset=us-ascii Just a quick question- can anyone tell me why putting your entire 300+ page manual into one FM file would make sense? I was always taught that splitting it out one file per chapter

RE: Large FM File

2008-05-02 Thread Combs, Richard
[EMAIL PROTECTED] wrote: I also have had problem-FrameMaker files where the author at the home office in Europe forgot to embed the images files before sending me the FM file. The result was lost time and effort. And to make matters worse, they sometimes sent me the image files themselves

Large FM File

2008-05-02 Thread Alan Litchfield
Hi Neil, Why do you ask? Have you been instructed to do this or did someone expound their worldly wisdom upon you? Alan Neil Tubb wrote: > Just a quick question- can anyone tell me why putting your entire 300+ > page manual into one FM file would make sense? I was always taught that >

Large FM File

2008-05-02 Thread Åsa Johansson
be very high. But I guess it is a better idea to stop changing file names and moving around text than merging all FM files into one. ;-) /?sa > -- > > Message: 5 > Date: Thu, 1 May 2008 14:32:50 -0400 > From: "Neil Tubb" > Subject: Large

Large FM File

2008-05-02 Thread John Posada
Why does seeing one example mean it makes sense? What does your training and experience tell you. On 5/1/08, Neil Tubb wrote: > > Just a quick question- can anyone tell me why putting your entire 300+ > page manual into one FM file would make sense? I was always taught that > splitting it out

Large FM File

2008-05-02 Thread Whites
>> Date: Thu, 1 May 2008 14:32:50 -0400 >> From: "Neil Tubb" >> Subject: Large FM File >> To: >> Message-ID: >> >> Content-Type: text/plain;charset="us-ascii" >> >> Just a quick question- can anyone tell me why putt

Large FM File

2008-05-02 Thread poshe...@bellsouth.net
- > > > > Message: 5 > > Date: Thu, 1 May 2008 14:32:50 -0400 > > From: "Neil Tubb" > > Subject: Large FM File > > To: > > Message-ID: > > > > Content-Type: text/plain; charset="us-ascii" > > > >

Large FM File

2008-05-02 Thread Combs, Richard
poshedly at bellsouth.net wrote: > I also have had problem-FrameMaker files where the author at the home > office in Europe forgot to embed the images files before sending me the FM > file. > > The result was lost time and effort. And to make matters worse, they > sometimes sent me the image

Large FM File

2008-05-01 Thread Neil Tubb
Just a quick question- can anyone tell me why putting your entire 300+ page manual into one FM file would make sense? I was always taught that splitting it out one file per chapter was the safest and best way to go, but I've just seen an example of the one large file approach. Does anyone else do

Large FM File

2008-05-01 Thread Milan Davidovic
On Thu, May 1, 2008 at 2:32 PM, Neil Tubb wrote: > I was always taught that > splitting it out one file per chapter was the safest and best way to go, > but I've just seen an example of the one large file approach. Does > anyone else do this? Just curious. I'm also curious -- did someone offer

Large FM File

2008-05-01 Thread Rene Stephenson
and output QA. :-) Rene L. Stephenson - Original Message From: Neil Tubb <neil.t...@solacesystems.com> To: framers at lists.FrameUsers.com Sent: Thursday, May 1, 2008 2:32:50 PM Subject: Large FM File Just a quick question- can anyone tell me why putting your entire 300+ page

Large FM File

2008-05-01 Thread Combs, Richard
Neil Tubb wrote: > Just a quick question- can anyone tell me why putting your > entire 300+ page manual into one FM file would make sense? I > was always taught that splitting it out one file per chapter > was the safest and best way to go, but I've just seen an > example of the one large