Thank you for the offer ‹ I gratefully accept!

I do not have any experience with Framemaker, so I welcome any information
on it. I thought I might also include a section on Apple¹s iwork suite.

Matt


On 5/26/08 3:59 AM, "Gary Schnabl" <[EMAIL PROTECTED]> wrote:

> Matthew Copple wrote:
>> > I will go ahead and start on the migration guide, then.
>> >
>> > Thanks!
>> >
>> > Matthew Copple
>> > [EMAIL PROTECTED]
> Matt,
> 
> If you care to, you could set up a work site on my now dormant forum
> site for the Migration Guide. That way, if you had others helping, they
> could create forum threads and keep down the mundane messages off from
> the main OOoAuthors or this e-mail list. The forum has some OOo
> categories already set up, and others could easily be created.
> 
> The previous Migration Guide was essentially based on conversions
> to/from MS Office, and to a much lesser extent on WordPerfect. However,
> There are other applications or suites that we neglected totally before.
> FrameMaker is still a major-league player, and although FrameMaker does
> not directly convert to/from OOo, working through a DOC file converted
> from an ODT file works fairly well, as long as some OOo functions are
> totally avoided.
> 
> I found that anchored OOo frames convert somewhat OK to DOC, but having
> even one such OOo frame in the ODT parent file will cause its further
> conversion from DOC to FM to freeze up my FrameMaker 7.0 to the point
> that I would have to resort to the Windows Task Manager to abort
> FrameMaker. It seems to be RAM related.
> 
> Maybe, the newer version, FM 8, works better as FM 7.x was not
> supposedly Vista compliant (it works OK on my Vista ThinkPad, though).
> However, when I used the FM 8 evaluation, it too reacted unkindly to OOo
> frames converted to a DOC file. The DOC file is OK on Word, but FM won't
> even open if OOo frames are present in the parent ODT file...
> 
> If you don't have FrameMaker or any experience with it, I and hopefully
> others could assist you in including any FrameMaker (or possibly also
> InDesign) migration. I have an older InDesign installation--version
> 2.0.2. InDesign was intended to replace FrameMaker, but Adobe apparently
> could not get InDesign to do the heavy lifting, major-league authoring
> of large books and such that FrameMaker does much better than MSO or
> OOo. Yet, I routinely do FrameMaker authoring with parent ODT files, as
> long as its (OOo) pitfalls are not employed.
> 
> Gary
>> > -- 
>> > Gary Schnabl
>> > 2775 Honorah
>> > Detroit MI  48209
>> > (734) 245-3324
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Reply via email to