This page contains exciting new features you can try now in eBook Toolkit 2016.
Important: Before you use any beta features, read your End User License Agreement.
How to get beta features: The eBook Toolkit will update within 24 hours of you running Microsoft Word. The features (unless otherwise noted) will appear in a tab labeled Beta Features.
Dec 2, 2016 – Two new exciting beta features!
We encourage you to use our forums to send beta feedback.
1. Exciting new beta feature: Convert tables to pictures!
One of the most popular feature requests is the ability to convert Microsoft Word tables to pictures (bitmaps). When eBook readers render a page, they are not very good at displaying tables, making your eBook seem less polished or worse, ending in getting a bad review.
With this new feature, the eBook Toolkit will read each table and convert it to a picture.
Do not worry! Your original Microsoft Word files will never change. See the next beta feature (below) to learn how you can get a copy of the Microsoft Word files that contain the picture changes.
Converting tables to pictures relies on a feature within Microsoft Word, meaning we may not be able to resolve all problems. Here are the issues we have encountered so far.
- Some tables with lines at the top or bottom may be cut off.
- The display resolution and graphics card on your computer have a direct correlation to the picture’s quality. If you are using a low-resolution computer and are not using ClearType Text, then fonts may not look as good as they could.
- If you are running Microsoft Word on a virtual machine within macOS, make sure you enable Retina Display options if that is an option.
- Microsoft Word automatically adds extra white space (padding) to the bottom of the table. We are investigating ways to resolve this problem.
- Some tables, even if they are full-width, may convert to a shorter width. We are looking into why this is happening.
- If you happen to be running on a double-resolution monitor, like running Windows on a Parallels virtual machine on a Mac, the tables may only appear as half the original width. Set your Windows or virtual machine to display as scaled rather than using the double-resolution mode.
- Embedded tables (tables within tables) convert to one single picture. We convert the outermost table to a picture, so it should look nearly identical to your embedded table.
- Since you are converting a table to a picture, eBook readers can no longer search for content within them. For this reason, we recommend you add captions to your table with keywords people may search for.
- As mentioned in the Known Issues section above, use the highest possible resolution on your computer when running the conversion because the quality of the table will rely on the quality of your graphics card.
2. New folder structure adds your eBooks to a specific output folder.
- The eBook Toolkit is following more best practices by compiling your eBook into a folder called OPS (that stands for Open Packaging Specification). The eBook files themselves (booktitle.epub and booktitle.prc) appear by themselves at the root of the folder.
- There is a new output folder called “MSWord” that eBook Toolkit will use if you want to save your original Microsoft Word documents to the output folder (see #3 below). This will be useful if you want a single folder with all your eBooks files and final Microsoft Word documents.
3. Save a copy of your Microsoft Word files to the eBook output folder
Using this option is useful for the following purposes:
- If you are using the new beta feature to convert tables to pictures, you may want a copy of the Microsoft Word files with the pictures, rather than the original tables. This feature saves your original files to the output folder with the pictures.
- When you are ready to do a final conversion and publish your ePub or Kindle files, you may want to zip up the contents of all your output files. This new feature is handy, so you do not have to manually copy your original files into the production folder afterward.
- Remember, the eBook Toolkit never modifies your original files, but it may save your files to the output folder with changes. For example, if you choose the new future to convert tables to pictures (see the previous section), then the document will only save the version with the pictures.