<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Thanks to all who replied, it's genuinely good to know there isn't a
magically simple way to do this that I was unaware of. If the
import filters are more robust, we definitely should look into
upgrading -- we hadn't so far because as non-structured users we
hadn't seen any must-have features in v10 or v11. <br>
<br>
Onward!<br>
<br>
Tori Muir<br>
<pre class="moz-signature" cols="72"><a class="moz-txt-link-abbreviated" href="mailto:tmuir@spot-on-creative.com">tmuir@spot-on-creative.com</a> | 650.430.8674
<a class="moz-txt-link-abbreviated" href="http://www.spot-on-creative.com">www.spot-on-creative.com</a></pre>
<br>
On 1/30/13 7:25 AM, Art Campbell wrote:
<blockquote
cite="mid:CAOW=E1e1NNJVi0e2s6DnqsgJYeicy9YN3hECVQp4gw4zQhLTUw@mail.gmail.com"
type="cite">A couple of points....<br>
<ul>
<li>I wouldn't work with the Word files at all if you have any
other options. RTF would be the way to go.</li>
<li>You should have the option to open the RTFs in Frame using
the Japanese RTF import filter. It's more robust than the
English RTF filter. Try that... </li>
<li>You're two frame releases behind current, and the import
filters seemed (to me, at least) to have been updated. You
should at least download the FM11 eval version and see if that
makes a difference, or find someone with current versions to
test for you.</li>
<li>You also have another option... Output from Word to PDF, and
then save that out from Acrobat to RTF. Not saying it'll make
much difference or what the formatting will look like, but
it's an option to look at.</li>
</ul>
<br>
Art Campbell
<a moz-do-not-send="true"
href="mailto:art.campbell@gmail.com">art.campbell@gmail.com</a><br>
"... In my opinion, there's nothing in this world beats a '52
Vincent and a redheaded girl." -- Richard Thompson<br>
No
disclaimers apply.<br>
DoD
358<br>
<br>
I support <a moz-do-not-send="true"
href="http://www.TheGrotonLine.com">www.TheGrotonLine.com</a>,
hyperlocal news for Groton MA.<br>
<br>
<br>
On Tue, Jan 29, 2013 at 6:27 PM, Tori Muir <<a
moz-do-not-send="true" href="mailto:tmuir@spot-on-creative.com">tmuir@spot-on-creative.com</a>>
wrote:<br>
> We've been maintaining a set of engineering specs for a
client for >10<br>
> years. The documents are large, 300+ page multi-chapter
books, with header<br>
> autonumbering that goes to 8 levels. About a year ago, client
requested we<br>
> give them the Frame content for one spec in Word so they
could do some<br>
> extensive edits. We did, and had not heard from them since.
They contacted<br>
> us 2 weeks ago, asking us to reformat the document. They'd
compiled all the<br>
> chapters into one 450-page Word doc and done 2-3 major
revisions over the<br>
> last year, all editing done by engineers and other folks with
no expertise<br>
> in long-document work. It's a bit of a mess.<br>
><br>
> Now they want us to re-convert it into Frame. What would the
recommended<br>
> workflow be? We want to do this as cost-efficiently as
possible for the<br>
> client, but also keep our Frame template pristine and the
data clean.<br>
><br>
> - We tried opening the Word doc (and sub-sections thereof)
in Frame (v9),<br>
> but Frame crashes.<br>
><br>
> - We have saved selected chunks of the Word doc to RTF and
imported to<br>
> Frame. On the plus side, paragraph formatting comes in OK,
and tables are<br>
> tables (there are a bazillion tables). On the minus side,
paragraphs with<br>
> TOC references get split into two, one empty one with the
reference marker,<br>
> then one with the text. This is a significant issue in a
manual whose TOC<br>
> includes all 8 levels of the aforementioned autonumbered
headers. Plus the<br>
> dreaded missing-font message occurs, and I hate trying to
track that down.<br>
> And I'm a bit uneasy about corrupted cross references and
other metadata<br>
> that have been round-tripped thru Word, had bad experiences
with that.<br>
><br>
> - We can also just blow the Word file out to plain text and
reformat.<br>
> Painful, but our Frame template remains clean that way. Or
maybe a hybrid<br>
> approach where we RTF the Word document, then use that to
copy tables from<br>
> (formatting them is time-consuming), and import the rest as
plain text...<br>
><br>
> Recommendations?<br>
><br>
> Tori Muir<br>
> <a moz-do-not-send="true"
href="mailto:tmuir@spot-on-creative.com">tmuir@spot-on-creative.com</a>
| 650.430.8674<br>
> <a moz-do-not-send="true"
href="http://www.spot-on-creative.com">www.spot-on-creative.com</a><br>
><br>
> _______________________________________________<br>
><br>
><br>
> You are currently subscribed to framers as <a
moz-do-not-send="true" href="mailto:art.campbell@gmail.com">art.campbell@gmail.com</a>.<br>
><br>
> Send list messages to <a moz-do-not-send="true"
href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a>.<br>
><br>
> To unsubscribe send a blank email to<br>
> <a moz-do-not-send="true"
href="mailto:framers-unsubscribe@lists.frameusers.com">framers-unsubscribe@lists.frameusers.com</a><br>
> or visit<br>
> <a moz-do-not-send="true"
href="http://lists.frameusers.com/mailman/options/framers/art.campbell%40gmail.com">http://lists.frameusers.com/mailman/options/framers/art.campbell%40gmail.com</a><br>
><br>
> Send administrative questions to <a moz-do-not-send="true"
href="mailto:listadmin@frameusers.com">listadmin@frameusers.com</a>.
Visit<br>
> <a moz-do-not-send="true" href="http://www.frameusers.com/">http://www.frameusers.com/</a>
for more resources and info.<br>
<br>
</blockquote>
</body>
</html>