Comparing WebWorks versions

Etzel, Gary Gary.Etzel at Advantica.biz
Thu Jan 26 03:52:16 PST 2006


> Ideally, we'd like to upgrade to the latest version of all software,
> including FrameMaker v7.2 and WebWorks ePublisher Pro. However,
> Sourcerer (which we absolutely rely on) does not yet support FrameMaker
> v7.2.  So for now we'll stick with Frame v7.1.

I've had several users verify that Sourcerer works with Frame 7.2. We have
not tested it ourselves, so we are not yet listing 7.2. as officially being
"supported" on our website (www.advantica.biz/sourcerer). I would recommend
that you try it again and then contact me if you encounter any problems. 

> Two of our team members are about to learn how to use WebWorks Publisher
> Pro to create and modify templates. (Current team members know only how
> to apply existing WWP templates.) However, at least one vendor I've
> consulted no longer offers training on WebWorks Publisher Pro version 7;
> it's simply too old. I'm wondering if we should upgrade to WebWorks
> Publisher Pro 2003 or WebWorks ePublisher Pro.

I would not recommend ePublisher Pro -- it is not ready for use with
structured FrameMaker. There are rumors that the next service release will
fix at least one major bug regarding structured cross-references. However,
support for element-based mappings, which was supported in past versions of
WebWorks and is an essential feature if you use structured FrameMaker, seems
to be a long way off. If you do decide to use ePublisher Pro, you need to
base your EDD solely on paragraph and character formats, and not use EDD
context rules to "override" those formats.

> There is one downside to upgrading: While our desktop publishers will
> have WebWorks Publisher Pro, our authors will have only the WebWorks
> Standard v7 that is included with purchase of FrameMaker. We previously
> found that if we created templates in WWP Pro 2003, authors using WWP
> Standard 7 couldn't output HTML using those templates. (That's why we
> "downgraded" our WebWorks Pro licenses to version 7.) Having authors
> capable of outputting their own HTML is a luxury for us, but not an
> absolute need.

You don't necessarily need a WebWorks license for each user. We only have
two copies -- one is for the person who maintains our templates, and the
other is installed on a shared PC that is available to any writer. All our
builds are done on the shared PC. So you might be able to set up something
similar to that.

Regards,

Gary




This e-mail, and any attachments are strictly confidential and intended for the addressee(s) only.  The content may also contain legal, professional or other privileged information.  If you are not the intended recipient, please notify the sender immediately, by return of email, and then delete the e-mail and any attachments.  You should not disclose, copy or take any action in reliance on this transmission.  

Please ensure you have adequate virus protection before you open or detach any documents from this transmission.

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________



More information about the framers mailing list