Here I just outline the options of this multi-channel publishing framework. You may want to move onto the companion document on EDD formatting.
File-Save as ..
It should work, i.e. you will have a file with the XML contents. The XML file has a style sheet declaration that points also to the generated CSS file (not XSL/FO!)
<?xml version="1.0" encoding="ISO-8859-1"?><?xml:stylesheet href="Stepbystep.css" type="text/css"?><Stepbystep><Doctitle>XML with FrameMaker + SGML Quick Guide</Doctitle> ....
The next steps are optional. I recommend learning how to author EDD formatting rules before you think about printing and exporting to PDF. EDD rules are not necessary for HTML and XML production only since you have to rewrite the CSS rules anyhow, so can as well do your CSS from scratch :).
WARNING: The stylesheet declaration in the generated xml file is wrong. It should read <?xml-stylesheet ...>and not <?xml:stylesheet href="quick-fm-xml-guide.css" type="text/css"?> (a "-" instead of ":"). Yet another annoying little "feature" of F+S. Don't forget this !
This is really important if you plan use XML client-side, because your document will really look ugly. Note that the HTML CSS is NOT the same as the XML CSS, so do NOT put the files in the same directory. I strongly recommend to lock the CSS file once you fixed it (or/and make a copy of it). The risk that you overwrite it when you generate a new XML file is important since each time you save xml as XML or Html you always create a CSS file too.
This is not supported by F+S. You have to do it yourself. Now what I want is a semi-automatic xml+css -> XSLT (XHtml) translator ....