Skip to main content
R
ramukneevan007
New Participant
May 30, 2013
Question

Unstructured Framemaker to DITA

  • May 30, 2013
  • 2 replies
  • 5248 views

 

I need to move my documents from unstructured FrameMaker to DITA docs. Could anyone explain me or point me a link about the step by step instructions to migrate from unstructured to DITA Docs?

PS: I have framemaker 10 license. My preference is not to spend any or more money to do this migration.

Expect Good response.

Thanks,

Naveen

This topic has been closed for replies.

2 replies

A
Anonymous
May 30, 2013

Russ is giving you good advice.  DITA offers many advantages, but it's not a magic solution.  It's probably not going to be completely expense-free either.

  • For topic-based authoring in general, you have to learn to think differently about how to write before you can realize gains. 
  • For DITA in particular, your authors will have to become familiar with XML and DITA in order to create topics. Authoring tools such as FrameMaker, DITA-FMx, or oXygen can help, but for practical puposes, they can't hide the XML completely. You'll also have to train authors on DITA elements and attributes, and techniques for using them.
  • To get output, you'll need to understand XSLT, CSS, and probably the DITA Open Toolkit and Ant. (DITA2Go is a strong alternative, but it's not in the XSL-based mainstream of DITA activity.)
  • To manage your topics, you'll need a decent Content Management System.

As for conversion: I've used both the conversion-table method and Mif2Go to convert unstructured Frame docs to DITA.  In my opinion, Mif2Go is easier to figure out, does a lot of the work for you, and does a better job on the conversion. It is well worth the modest expense. But if you want to use the conversion-table method, I would start by defining a few conversion rules for your major paragraph tags, see what you get, and take it from there. It took me about 35 iterations to get a reasonably decent conversion table for my tag set.

Ether way you will almost certainly have to make some manual touch-ups.

(EDIT) If you're looking for information on how to create a conversion table, you'll need the Structured Application Developer Reference (Chapter 4).

http://help.adobe.com/en_US/FrameMaker/9.0/StructuredDev/Structure_Dev_Reference.pdf

R
Russ Ward
Brainiac
May 30, 2013

Hi Naveen,

There is no such thing as step-by-step instructions to do this. There are broad concepts, such as:

- Using conversion tables in conjunction with the DITA EDDs/templates to make the conversion

- Using a third-party app such as Mif2Go (http://www.omsys.com/dcl/mif2go_main.htm)... I think that's the right Omni Systems app.

But I am sensing something else... that maybe you need some more knowledge in this area before attempting such a task. This type of migration is a very big deal and a significant effort. To approach it without the proper planning and expertise is a good way to fail in the long run.

Have you done the proper analysis for this? Why the choice of DITA in the first place?

Russ

[The current link to the Mif2go site is: http://mif2go.com/ ]

R
ramukneevan007Author
New Participant
May 30, 2013

Hi Russ,

First of all thank you for the resposne.

My company wants to migrate from unstructured to structured DITA authoring so as to reap the benefits of DITA (Topic Based Authoring, easy management of docs, Content Reuse...and many more).

I have done research and analysis of this migration and understood the concepts of EDD and Conversion tables. But what I need is:

1. What are all the action items required for this migration?

2. Where should I start and where should I end ?

Thanks,

Naveen

R
Russ Ward
Brainiac
May 30, 2013

Unless you plan on doing DITA conversions as part of your job description, you will almost certainly spend more money (and absolutely spend too much time) learning the process of converting data from *any* application to DITA than if you have someone else do this for you.

At a minimum, you should consider mentoring (of the paid variety) to learn the process, and help you with the concepts.

One observation: DITA focuses on the topic, and combines them into larger pieces. "Traditional" documentation focuses on the book, or chapter, and breaks these down into smaller pieces. Understanding the basic building units will speed your understanding of DITA's strengths (and weaknesses).

-Matt

Matt R. Sullivan
co-author Publishing Fundamentals: Unstructured FrameMaker 11


Matt,

There is some truth in what you say, but I disagree with the general sentiment. Certainly, if you are a newbie, you might spend up a bunch of time (which equals $$$) figuring out how to do it. However, if done with diligence, that is never a waste. You grow in your professional knowledge and your employer benefits from a higher-skilled workforce. These technologies are critical to the future of technical publishing, so the more people in the field that understand them, the better. You won't get that understanding by paying somebody else.

Additionally, I disagree that you have to pay a teacher, unless you are in some massive hurry in which case the project is likely to fail anyway. I can do conversions in my sleep now, but not because I paid anybody to teach me. It's because once I was just like any newcomer, with a huge job to accomplish and zero knowledge about how to do it. Rather than pay an outsider, I (and couple others) was given the time to figure it out. Sure, it took a good long while that first time, but the professional growth that resulted was a big benefit to everyone involved. And the next time was easier (and there will almost certainly be a next time).

So, I don't mean to be confrontational. I just want to emphasize that the key to success is motivation and time, not a PO for a contractor.

Russ

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices