Frequently Asked Questions

This page is designed to provide answers to general questions that many of our customers and potential customers ask.

For product feature and functionality questions please consult the Community Help (Wiki), Archived Technical Notes and/or Official Product Help.

Most Popular Product Questions:

What version of ePublisher am I running? When was it released? Is it Supported?

To determine which version you are running, select Help > About, then compare your version and build number against ePublisher's version history.

Does ePublisher support FrameMaker?

ePublisher currently includes support for the following versions of FrameMaker:

  • FrameMaker 2017 - Supported since ePublisher 2017.1
  • FrameMaker 2015 - Supported since ePublisher 2015.1
  • FrameMaker 12 - Supported since ePublisher 2013.3
  • FrameMaker 11 - Supported since ePublisher 2012.3
  • FrameMaker 10 - Supported since ePublisher 2010.4
  • FrameMaker 9 - Supported since ePulisher 2009.2
  • FrameMaker 8 - Supported since ePublisher 2008.1

Can I use FrameMaker 8 with ePublisher?

Yes, however FrameMaker 8 is no longer certified by WebWorks and is not covered by WebWorks support agreements.

Does ePublisher support Windows 8?

Yes, support for Windows 8 was officially added in the 2012.3 release.

Does ePublisher support Windows Vista and Windows 7?

ePublisher no longer supports Windows Vista. Windows 7 SP1 and above is fully supported.

Does ePublisher support Word 2013?

Yes, both the 32-bit and 64-bit versions.

Does ePublisher support word 2010?

Yes.

Does ePublisher support word 2007?

Yes, however it is deprecated as of the 2017.1 release.

Does ePublisher support 64-bit?

Yes, with release 2008.4 and greater.

Does ePublisher support .NET technology?

ePublisher currently supports .NET and all the languages that run on .NET platforms.

What is the difference between the old WebWorks products and the ePublisher Platform?

Although both our legacy WebWorks products and the current ePublisher platform allow a user to convert content into a form for online delivery, they are two seperate, completely different products.

The legacy WebWorks products were built using a closed architecture and relied on a proprietary macro language to enable users to achieve the outputs they desired. While extremely effective at the time, this approach resulted in limited growth potential for the product and did not provide the flexibility required to meet developing changes in the ePublisher industry.

The ePublisher platform is an open architecture built on industry standards like XSL. This gives the product greater flexibility, allowing for more functionality, high degrees of customization, and the ability to work with new content types and standards such as DITA-XML. The component-based design of the ePublsiher platform ensures that a document designer techincal author, or production specialist can work with tools tailored for their particular workflow needs.

What does your product numbering scheme mean?

With the SPRING 2008 release of ePublisher the product numbering scheme was changed to reflect the quarterly release schedule. Product numbering now reflects the year and the quarter of release. The SPRING 2008 release is numbered 2008.1; the SUMMER release was numbered 2008.2, etc.

What is the WebWorks product release schedule?

The WebWorks team is currently committed to providing four releases a year on an approximate quarterly schedule.

How can I find out what changed between different versions of ePublisher?

The readme.txt file located in the base directory of the ePublisher installation lists all updates and changes going back to ePublisher version 9.0.

How is the ePublisher platform licensed?

ePublisher is licensed based on the total number of people that have installed and activated the software. For a full definition of licensing terms please refer to the License Agreement.

Product Development

What are your plans to support any additional output formats?

The WebWorks.com team constantly monitors and asseses new output formats. New formats are included in the product roadmap based on market and customer demand. When the decision is made to include a new format in a specific product release it will be announced on the website and in the newsletter. It is our intention to introduce at least one new output format per calendar year.

I know you support DITA, but what about other XML standards such as S1000D, SCORM etc.?

Although ePublisher is shipped with with an XML adapter preconfigured for DITA it can be extended and adapted to meet other XML architectures. We are continually monitoring the market demand and uptake of other standards and will make decisions on providing packaged solutions based on market and customer demand. In the interim we can help you develop one-off XML based solutions through our Services offerings.

Why did WebWorks Standard Edition disappear from FrameMaker?

As mentioned above, the legacy WebWorks products had reached the end of their development path. A mutual decision was made with Adobe to discontinue shipping it as a bundled product with the next release of FrameMaker. The WebWorks.com and Adobe teams continue to work together to make sure that ePublisher is an essential component in any FrameMaker-based multi-channel publishing solution.

Quadralay / WebWorks.com Questions

What does it mean when it say's "Made with the ePublisher Platform"?

Every page on the new-look WebWorks.com site carries a "Made With the ePublisher Platform" button and logo. Yes, we used our own products to build this site. Content was written in a mix of FrameMaker, MS-Word, and a selection of DITA authoring tools by contributors from across the company. The ePublisher platform was then used to combine that content and deliver HTML pages predefined to conform with the new appearance and layout.

Why the new WebWorks.com branding?

Since the very beginning Quadralay has been involved in many different aspects of online delivery and internet infrastructure. A polling of a cross section of our customers during late 2006 and early 2007 showed that the majority of customers using our products in the ePublishing industry thought of the company as WebWorks rather than as Quadralay. Based on this the decision was made to group all our ePublishing online delivery products and services together under the WebWorks.com brand.

Where did the name Quadralay come from?

Our most excellent name was chosen when our founder found himself sitting among a pile of hard drives and corn chips: Quadra hard drives, and Frito-Lay corn chips.