Frame vs Arbortext

[eric.dunn at ca.transport.bombardier.com]

Steve Rickaby <srickaby at wordmongers.demon.co.uk> wrote on 04/27/2007 
05:19:00 AM:
> At 11:46 -0700 26/4/07, Matt Sullivan wrote:
> >These days, Frame can work directly with the XML, and storing as .fm is
> >strictly optional. IMO, this undercuts much of AT's sales pitch.

And the most annoying thing is that working 'natively' with XML is a red 
herring. Because the only thing that has changed is that when your 
workflow is to include FrameMaker functionality and strengths until 
delivering xml you name the file FileName.fm and if you want to always 
roundtrip you save the file as FileName.xml.

The only difference is FrameMaker automatically assumes "Save-as" when the 
original file opened was FileName.xml. Big Deal.

> If the [fairly imminent?] upcoming version of FrameMaker actually 
> turns out to be FrameMaker 8 and not FrameMaker 7.2-and-a-bit, it 
> seems likely that the developments will lean heavily in the 
> direction of XML support, and this will further erode what different
> currently exists.

And those differences are only in approach. I could only roll my eyes and 
turn up the sarcasm as an AT rep explained to me the "difficulties" of 
EDDs and of not working "natively" in XML. I was dismissive as possible 
when they couldn't find a comeback to my question about how does the 
complexity and "non-nativeness" of EDDs compare to the development of 
FOSIs and AT display and print engines.

Pathetic really.

Eric L. Dunn
Senior Technical Writer

_______________________________________________________________________________________________________________ 

This e-mail communication (and any attachment/s) may contain confidential 
or privileged information and is intended only for the individual(s) or 
entity named above and to others who have been specifically authorized to 
receive it. If you are not the intended recipient, please do not read, 
copy, use or disclose the contents of this communication to others. Please 
notify the sender that you have received this e-mail in error by reply 
e-mail, and delete the e-mail subsequently. Please note that in order to 
protect the security of our information systems an AntiSPAM solution is in 
use and will browse through incoming emails. 
Thank you. 
_________________________________________________________________________________________________________________ 


Ce message (ainsi que le(s) fichier/s), transmis par courriel, peut 
contenir des renseignements confidentiels ou protégés et est destiné à 
l?usage exclusif du destinataire ci-dessus. Toute autre personne est par 
les présentes avisée qu?il est strictement interdit de le diffuser, le 
distribuer ou le reproduire. Si vous l?avez reçu par inadvertance, 
veuillez nous en aviser et détruire ce message. Veuillez prendre note 
qu'une solution antipollupostage (AntiSPAM) est utilisée afin d'assurer la 
sécurité de nos systems d'information et qu'elle furètera les courriels 
entrant.
Merci. 
_________________________________________________________________________________________________________________