Re: .fm vs .e## vs .xml

["Lynne A. Price" <lprice@xxxxxxxxxxxx>]

At 03:05 PM 3/31/2005, Webmaster wrote:
> 1) Is there a way to setup FM to it can simply edit XML files in FM's
> structured mode? (instead of importing .xml, converting to .fm and
> reexporting to .xml)

LN,
  In FM 7.0, when the user opens an XML document, FM converts it to an 
internal form. The user can then save it as a binary FM file or convert it 
back to XML. In FM 7.1, the internal processing hasn't changed, but FM 7.1 
remembers when a file originated as XML and automatically converts the 
internal form back to XML when it is saved.


> 2) Is there a way for FM to create .xml files instead of a bunch of .e##
> files?

When saving a book to XML, FM processes each book component separately. It 
creates an XML document for the entire book that references an entity for 
each book component. If you want complete XML documents for individual 
components, you can save them to XML one at a time. With a little bit of C 
programming, it is also possible to change the book export behavior to 
produce this result.

        --Lynne



Lynne A. Price
Text Structure Consulting, Inc.
Specializing in structured FrameMaker consulting, application development, 
and training
lprice@xxxxxxxxxxxx            http://www.txstruct.com
voice/fax: (510) 583-1505      cell phone: (510) 421-2284 



** To unsubscribe, send a message to majordomo@xxxxxxxxx **
** with "unsubscribe framers" (no quotes) in the body.   **