TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Sadly, there's a level at which specific instructions can't be given. The actual steps depend entirely on your target EDD, the current template you're using, and how well the template was adhered to. I guess there are a few pointers, though.
First, there should be no difference between generating structure in 7.0 vs 10 or 11. The ideas are the same. So if you're discovering problems with an old work flow, then you should look for what has changed in your legacy docs, or your EDD.
Second, start with a really small document that only has one part of the structure. Maybe start with a H1 and a body paragraph. Get that to generate the correct structure. Then add something else... Build it up incrementally until you have a full document working. Save tables for last. It's very difficult to start with a complete table that doesn't work and figure out where the problem is. It's much easier to build up from a small table that works. So I'm suggesting you start a new conversion table, and work up to a full solution from there.
The Adobe docs do tell you how to nest elements. You'll need to understand that. Also, use labels to identify pieces for more conditional effects when wrapping things up. All that should be in the docs.
You may never get 100% satisfaction in every case. You'll have to check your work anyway. So if you have to manually fix a thing or two, so be it. Think of the 80/20 rule... 80% of the process can be implemented with 20% of the effort. Then implementing that last 20% of the process will consume 80% of the effort. Unless you plan to sell a product, somewhere after 80% and before 100% you'll find a threshold of diminishing returns. Cash in your chips and be happy.
I am restoring a 7-part recorded Webinar series on structured FrameMaker that was done by Tom Aldous with FM10. Watch for an announcement with the link posted to this group sometime tomorrow. You will find this series very useful.
On Jun 4, 2013, at 7:04 PM, "William Sherman" <bsherman77 -at- embarqmail -dot- com> wrote:
> I know many of you have gone on to better things, but I'm working with Frame again and ran into an issue.
>
> The last structured FrameMaker was mostly all structured documents in FrameMaker 7.2. Six years ago, I was someplace that was converting from unstructured to structured in 7.0, I think. I don't remember an issue trying to convert unstructured files to structured ones.
>
> However, in FrameMaker 10, we are having issues getting unstructured documents to convert to structured. We already have an EDD. We have gone through and created the conversion rules table and adapted it to our EDD and structure.
>
> Yet when we convert documents, the structured view frequently has element names that are not valid in our structure (the table should handle that) and are usually not in a staggered outline but a single line and red.
>
> Granted, a couple of us have only put in a couple of days to do this, but IMVHO, this is the sort of thing that should be very much automated and has instead been very manual for us.
>
> And still no good results.
>
> The Adobe instructions we have found lack several steps. We have managed to figure those out and fill them in. Most sites in Internet searches pop up regurgitated Adobe instructions. No one so far seems to answer why we haven't ended up with a final structured document that doesn't require 8 hours of massaging to be like our other structured docs.
>
> Anyone have a nice set of instructions that really work?
>
> Thanks.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
