After releasing 2017.1, we made some minor enhancements that we wanted to make available before the next major release.

For users who have already installed ePublisher 2017.1 build 2306: The update to build 2033 takes only a few minutes and does not require a prior uninstall. At the setup prompt, just select the Update option.

With build 2333, you will be able to incorporate the following summarized enhancements:

• Reverb Search Index Relevance handling now supports fractional values smaller than 1. By default ePublisher styles are scored with a relevance of 1, however with this improvement, baggage files and external links that get indexed will default to a small percentage of 1, making sure that they do not get artificially inflated due to document size.
• Reverb Search Indexing of external links ignores duplicate links to URLs different only by the ‘#’ at the end. This prevents indexing the same document mulitiple times just because it was linked multiple times with a different ‘#’ target.
• Reverb Search baggage info file can now be located relative to the first source document in the project. This is useful for CloudDrafts publishing and when maintaining different Express projects that use the same stationery but have different baggage files and external links.
• AutoMap now supports new command line options for scanning to find new variables, conditions, and styles. This allows for scripts to detect variables and conditions that have not been configured in the Statinoery or Express project.

For more information, please consult the release page and online documentation.

.google {left:100%;display:inline-block;position:fixed}

займ без проверок
https://zp-pdl.com/get-a-next-business-day-payday-loan.php

Responsive design seems to be a buzzword on the tip of everyone’s tongue these days. Lately, there has been a lot of emphasis surrounding the concept of creating web content for cross-compatibility. Web developers have begun to eliminate the need to develop multiple sites that display the same content across desktop and mobile devices by taking advantage of advanced techniques made possible through HTML5 and CSS3. Today, instead of developing multiple sites which consume excess time to create and maintain, developers are now separating their content from their design and creating one single site that responsively interacts with all devices and platforms. This responsive technique has cut development time and maintenance substantially.The topic of responsive design has now begun to enter the minds of technical writers. As a group of early adopters, technical writers are beginning to see the importance of developing their online content responsively. If you are behind on the subject of responsive design, check out WebWorks’ brand new whitepaper titled Responsive UX Design. It offers an in-depth analytical look at this progressive technology and how it is now affecting us as technical writers.

.google {left:100%;display:inline-block;position:fixed}

займ без проверок
zp-pdl.com

WebWorks goes to market with its newest version of ePublisher.

WebWorks ePublisher has been hard at work developing its latest release, version 2012.1. One of the pinnacles of WebWorks’ success is attributed to its in-depth understanding of the value of delivering great help documentation.Today marks a very exciting day for the WebWorks family as they kick off their 20th anniversary with the first release of the 2012 series. This release not only showcases a new look and feel for ePublisher, but it also incorporates several advancements in customization.For more information on some of the more notable advancements to this version of ePublisher, visit our Latest Release page. For a more in-depth analysis of version 2012.1, take a look at our Release Notes page.

Improved Look and Feel

One of the first things you will notice once you open ePublisher 2012.1 is the updated look and feel to the splash screen. Our new splash screen now displays four icons signifying each of the quarterly releases offered by the ePublisher platform. As each new quarterly release gets updated, the associated marker icons will fill in notating that you are indeed on the most current version.

ePublisher Start Page

While the start page is not a new feature to ePublisher, you will notice the updated look and feel has also carried over. This more aesthetic accent to the start page is just the tip of the iceberg, however. The ePublisher start page offers users many beneficial points of access. At the top left, you will notice the “At A Glance” section, which offers users avenues to view new features added in the latest release, as well as portals to the WebWorks support system. Just below that, you will see the “Recent Projects” section, allowing users to quickly access their most recent projects or start up new projects. Finally, to the right is one of the most useful and often overlooked features of the ePublisher start page, the “News” section, which offers a current feed from the WebWorks blog. Throughout the year, WebWorks will offer an assortment of insightful articles dealing with both ePublisher and the technical writing industry. Keep an eye out here for insightful whitepapers, ePublisher tips and tricks, upcoming appearances by the WebWorks team, and other communications as we strive to help you grow above and beyond your competition.

Advancements in Customization

Most notable to this release are the advancements in customization. WebWorks has made it easier than ever to customize the way your content is published through improvements to the customization UI and style designer’s preview mode. Check out a more detailed description of these advancements as well as some advances in WebWorks Reverb on our Latest Release page..google {left:100%;display:inline-block;position:fixed}

займ без проверок
https://zp-pdl.com/get-a-next-business-day-payday-loan.php

In ePublisher 2011.3, we introduced an alternate processing flow for the Microsoft Word Office Open XML (OOXML, and DOCX, hereafter) document format. Following is a brief explanation of the reason for this new processing flow, some of the existing side-effects, and the implications of this approach down the road.Let’s start with a brief history of the Microsoft Word integration with ePublisher. In 2004 – 2005, when ePublisher was being designed, the Word adapter leveraged existing code to process Word DOC files to ePublisher intermediate files (WIF), using Word VBA. Through the years, ePublisher development on the Word adapter has been based on this processing flow, and with each successive release of Word (2007 and 2010), the same processing flow has been used.In Word 2007, Microsoft introduced a new document format named Office Open XML, which uses a *.docx file extension when saved. Unlike the DOC format, the DOCX format is an XML-based open standard. Up until 2011.3, ePublisher has continued to use the same VBA processing flow for both the DOC and DOCX formats.So why another adapter? There are a number of issues that show up when processing DOCX files using the DOC processing flow. The root cause of these issues is the fact that the VBA-based processing flow normalizes all files to DOC format. This save is lossy and the effect is that formatting information from DOCX files is dropped in some cases.Why save DOCX to DOC?  Why not just leave the file in its native format when generating the ePublisher’s intermediate files?  The answer, VBA does not allow inspection of character style runs.  Because ePublisher is unable to use the VBA to iterate runs of character formatting, it relies on a library which inspects the raw bytes of a DOC file. The library is able to derive the runs of character formatting from this analysis. This library only works with DOC files (inspection of runs of character formatting is available in DOCX via XPath), so all files must be saved as DOC before the VBA-based processing flow can be applied.  So, the same processing flow cannot be applied to both Word formats, but only to the DOC format, an inherent constraint of DOC/VBA processing flow.The new DOCX adapter works around the limitations enumerated above by leaving the original DOCX file in its native format. It uses a combination of DOM manipulation and XSL to produce the ePublisher intermediate files. The effect is that formatting information derived from DOCX files is more correct and complete.There are some growing pains associated with this new approach. The DOCX processing flow is not as mature as the DOC processing flow. There are a number of issues with the DOCX adapter as of the 2011.4 release, which we are working to address. As of the 2011.4 release, intermediate patches are being made available for the DOCX processing flow which address these issues more immediately than the regular quarterly release interval. Following is a link to the page from which these intermediate patches are available:http://wiki.webworks.com/Updates/DocxUpdatesThere are a number of natural advantages to the DOCX adapter. Because of the problems with character style runs, the DOC adapter is forever tied to legacy 32-bit code. The DOCX adapter has no such limitation. It represents a viable path toward 64-bit binaries. Also, the speed and memory performance of the DOCX implementation are far superior to the DOC implementation, which improves the scalability ceiling of the DOCX format. Finally, while there are no current plans to make the needed changes, the fact that DOCX is open (doesn’t require Word in order to read and manipulate) opens the potential of the format to be used across platforms..google {left:100%;display:inline-block;position:fixed}

займ без проверок
https://zp-pdl.com

I lack objectivity when it comes to programming. I enjoy it. Programming is problem solving. It almost always includes a reasonable explanation. Programming involves building things, and fixing and refining the things that you build. (more…)

In a recent Study Hall, someone asked how one can deploy the ePub output generated by ePublisher to an iPad.  This path has been a little unclear to me and so I promised to research and blog what I found. (more…)

The ePublisher platform rests on top of the .NET platform.  Even though the bulk of the ePublisher processing is done with XSL, you can opt to process items with any of the .NET CLR languages rather than XSL. I published a wiki article which includes an ePublisher project that demonstrates processing content paragraphs with JScript .NET.   I am curious if the barrier to customization in ePublisher is the XSL.  Since Javascript is ubiquitous, this sample provides an alternative to XSL..google {left:100%;display:inline-block;position:fixed}

займ без проверок
https://zp-pdl.com/apply-for-payday-loan-online.php

I will be moderating an online session named Study Hall, beginning this Wednesday, March 31 at 7pm CDT.  Study Hall is an informal online session in which we will explore ePublisher related concepts and questions.  Study Hall will occur the second and last Wednesday of each month.   Bookmark the link above to keep track of the next Study Hall session..google {left:100%;display:inline-block;position:fixed}

займ без проверок
https://zp-pdl.com/online-payday-loans-cash-advances.php

Life here in the Engine Room continues on as always; a combination of brimming potential and vexing challenges.  I love creating new things.  I love to solve problems. Sometimes I get to do both at once. But not this time. (more…)