If you want to contact QSystems, please use the following form:

Please enter your name.


Please tell us how we can help.

Español

Today the main issue is that every editorial hoards hundreds or thousands of publications in QuarkXPress or InDesign format that would put in eBook format.

Possibly the most used way to produce eBooks is to use Adobe InDesign. The problem that arises is the approach. Building eBooks from InDesign is a good way to produce them, if we analyze the process only from a technical standpoint. In fact, eBook Factory does exactly the same. The difference is in other aspects, very important in this new business.

Benefits

Firstly, eBook Factory produces virtually any eBook format. This is because it extracts all graphic and textual material from InDesign in all its richness, and brings them to its database. That is, does not directly produce "XHTML for Digital Editions," but produces content in a "template format" that can be transformed to any other.

As an example, the Mobipocket format can occur while the epub or another. You can even generate different types of epub targeting different eReaders, if desired. Therefore, you can forget what will be the winner format or their evolutions. Having the XML and JPG of your books in a database, you are able to export again anytime. Definitely a nightmare less for the editor.

Second, the cost. Almost all systems and ways to produce eBooks require technical skills. eBook Factory too. The difference, again, is in the industrial approach. With InDesign (or Calibre, Stanza, or other systems), each person producing eBooks need that knowledge. And this means one thing: or slow production or very expensive production. eBook factory solves this allowing labeling task to non-technical personnel. Technical knowledge is incorporated into the system using XSL and CSS, grouped in eBF under the form of "export styles". Thus, the cost of technical resources is shared between all books of a collection, or even an editorial. This workflow not only minimize production costs but also technical tasks.

Thirdly. The cost. Yes, the cost again. Because not only is matter of cost reduction and to good roles sharing. To obtain an epub from InDesign, for example, you have to do some extra work: local formats, tables of contents, fonts... For new books is possible afford that extra cost. But does that mean that you need to spend hours of previous work for each of your books, before you can make an eBook? No, if you use eBook Factory. This is due to several reasons. A couple of examples: eBook Factory extracts "rich" XML from InDesign. All formatting and typographic control is incorporated into the XML, so the system can produce very well formatted eBooks without having to do extra work in InDesign. And the images. We do not mean normal images that can appear in a document. InDesign export images very well. We mean those box based assemblies, lines and strokes that are not really an image. Or tables that can never be the same in InDesign and XHTML. eBook Factory export JPG automatically from those assemblies. These are just some of the advantages of eBF industrial system.

Finally, the tactical advantages. eBook Factory is part of an editorial system. It is not just a format conversion tool. In this system lies the full potential of a cross media publishing system. If someone wants to create HTML pages, or to connect this production system to the platform to sell eBooks, or integrate suppliers or freelancers in the workflow... will only find benefits in eBook Factory. Many modules are available to add to this system. After all, you can have a complete book manager from which regenerate any ebook simply editing InDesign documents. The limits of work with this system are truly open.

Technologically, eBF is located on the same level as the most common solutions. Where it excels is in the use of this technology, in its industrial approach, and in its careful design as part of something bigger.