RE: FrameMaker Release 7.2

["Steve Whitlatch" <swhitlat@xxxxxxxxxx>]

> That, however does not mean there isn't a solution
> which avoids this impasse. Such a solution would
> require that XSLT production would be accomplished
> "under the hood" within FrameMaker itself by providing
> the capability to dirctly convert an EDD's format
> rules into an XSL instance, 

The Arbortext Styler product converts user input from a 
mostly point-and-click GUI interface into a stylesheet that 
can be exported as an XSL stylesheet for XSL-FO (page composition),
an XSL-HTML stylesheet for HTML output, or a FOSI stylesheet for 
either page composition or the on-screen editing view. It is a 
very expensive add-on to an already expensive product. I think it 
may be intended to reduce the high costs of heavy IT involvement. 

Of course because FrameMaker does WYSIWYG, PostScript, and 
PDF quite well, it does not need any similar product. This 
is very good! And the price is better. The big bummer is  
with all of FrameMaker's import, export, and validity problems. 
Where Epic Editor is weak, FrameMaker is strong, and vice-versa. 

Steve Whitlatch

  

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