Adobe Technical Communication Blog

In this Blog, I will talk on how the Authors can leverage Unstructured FM Knowledge to author structured DITA content in FrameMaker. As authors move to authoring structured or DITA content, they can use the existing knowledge of Unstructured FM workflows to author the same. This helps in quick ramp up and reduces the barrier to move to structured or DITA content.

Working with Objects:
As authors create structured content, author need to take care of managing elements and attributes apart from authoring content. With Adobe FrameMaker, this additional complexity is automatically handled by the application itself. Authors can use the existing workflows for working with Objects like XRef, Images, Tables, Footnotes, Indexterm etc. FrameMaker will automatically insert the corresponding elements for these objects in the hierarchy.

Working with DITAMaps:
In DITA, DITAMaps acts like container to specify the order and link content of documentation being authored. Authors can work on DITAMaps in the same was as he / she used o work on FM Books. With FrameMaker you get workflows similar to BOOK to create and edit DITAMaps.

The following demo will demonstrate these similarities.
View in separate window

Thanks!
Rajat Bansal
Engineering Manager – Adobe FrameMaker

FrameMaker,Technical Communication,Adobe Technical Communication Suite,FDK

In this blog, we are going to talk about the correct way to use FDK resources.

All Structure Import/Export clients have to link with structure lib(struct.lib) and its dependent resource file(fmstruct.res). These files(struct.lib and fmstruct.res) are shipped with every version of FDK, and to link with the above mentioned files, you should add them to the Additional Dependencies field in your client’s project setting. This is the recommended way to link with structure lib and its resources.

In case, you have embedded the structure resources(fmstruct.res) into your client’s project as a resource script file(.rc), then after upgrading your client to link with newer version of FDK, your client may behave unexpectedly. This may happen because, structure resources and their index in string table may change with every new version of FDK. If you are following this approach, then don’t forget to update the embedded resources in your client project.

Please write a comment if you’ve any doubts/questions.

Thanks!
Harsh Gupta
FrameMaker Engineering

pageTracker._initData();