On Thu, 11 Jan 2007 10:56:46 -0500, <Michael.Long at thomson.com> wrote:

>Mif2Go rtf output is "editable" but it depends on what that consists of. 
>Mif2Go basically strips the automation from the file and puts in manual 
>characters. 

Not always.  Where Word doesn't offer anything close, we do
output the Frame content as plain text.  But for autonumbers
and xrefs, for example, there are other options.

>For example, all bullets and numbers in lists are like keyed entries. You
>can attach and load your Word template, apply an automated style, but
>you will still have the hard bullet or number to deal with. For
>extensive or long term "editing" there will need to be a clever
>automated method of removing the manual bullets and numbers. Unless
>someone knows a trick that I don't.

We considered supporting Word's regular "bullet and numbering"
feature, but decided not to because it is really unstable,
especially for large docs such as those commonly produced in 
Frame.  When you are producing Word docs for review purposes,
it's really best to use the default plain text, as that way
you can find the matching Frame para more easily to make any
corrections.  If however you are migrating to Word, you can
choose to use SEQ fields which closely emulate Frame's own
autonumbering.  That's what Word power users prefer, so Mif2Go
does produce them automatically on request.  SEQ fields are
stable, and easily copied for new paragraphs.

>Also cross-refs and variables become keyed characters, rather than
>automated, 

By default, xrefs remain *live* xrefs, with added hyperlinks
to emulate Frame capabilities.  You can make them plain text if
you prefer.  Variables are not well supported in Word, and do
become plain text.

>and I think the  non-breaking space or something in Frame
>cross-refs is turned into a sort of o reverse bullet. Someone will want
>those removed. 

Sounds like you have Word's settings to view special characters
on.  You control that in Word, under Tools | Options | View.
We also use Word hidden text to support features that Word
doesn't allow directly, like refs to page numbers in another
document.  If you turn on viewing of hidden text, you'll see
those; or you can turn off that Mif2Go feature and get plain
text page numbers.  Your call.

>There are other matters I don't immediately recall.
>Someone will also want to resave the rtf output as doc before
>editing--the rtf becomes unwieldy. 

True, especially if you have large bitmaps with 24-bit color
("millions of colors"), for which RTF lacks any compression,
or if you want to support multiple Word versions conveniently.

>There are other limitations I don't recall offhand. But if you just want
>a Frame format mirrored in Word, for temporary use, Mif2Go does well.
>Definitely try it first to see if it will work for you and yours.

Thanks!  Those interested can download the current demo version:
  http://www.omsys.com/dcl/download.htm

HTH!

-- Jeremy H. Griffith, at Omni Systems Inc.
  <jeremy at omsys.com>  http://www.omsys.com/

Reply via email to