Help+Manual News

Beta Test: Cloud-based HM Translation with Smartcat

Smartcat is a cloud-based translation ecosystem that is already widely used, supporting both advanced machine translation and translation by traditional human translators, or a combination of the two. Recently, customers have started asking the staff at Smartcat whether the system could process Help+Manual XML topic files. They looked into it, contacted us for the specifications and the result is now a working beta version that is ready for testing.

Call for beta testers

If you are looking for alternative ways to translate your Help+Manual documents you are invited to participate in the free beta test of the new Smartcat system. Pavel Doronin and his team would really appreciate your feedback and suggestions for possible improvements.

How to participate

You just need to register an account at Smartcat, or use your existing one if you already have one. Then send Pavel Doronin your registration email address as a direct message within the system, or to the Smartcat support team at support@smartcat.ai, with a request that we enable Help+Manual support in your account.

About H+M support in Smartcat

Currently you can import individual/multiple XML files (both topic files and TOC files), not entire projects. You can then translate them yourself, assign them to a translator or apply machine translation. Both H+M’s traditional XML and the new TidyXML introduced with version 7.3 are already fully supported.

Full project import may be added in a future update. Any and all other suggestions you may have are very welcome, of course.

No Comments

Broken YouTube videos in CHM – and how to fix it

With Help+Manual 7 we have introduced web-based videos like YouTube and Vimeo for embedding videos in help files. Especially YouTube worked like a charm in CHM files – until recently.

After a change in the YouTube scripts, the videos – when clicked to play – might trigger a Javascript error. The reason for this error is, that the script expects a “newer” version of MS Internet Explorer, it requires MSIE 9 as the minimum.

The Windows HTML Help viewer internally uses the rendering engine of MS Internet Explorer to display CHM files. By default, it runs with MSIE 7, even if a newer version is installed. To force the CHM viewer to use a newer rendering engine, it can be elevated with a HTML meta tag. We do this with all our CHM templates and skins, and the default elevation for CHM files was MSIE 8 so far. With the recent change in the YouTube scripts, it requires MSIE 9 or higher.

 

A quick and easy fix

To fix the YouTube problem, you need to apply a small change to the skins or HTML templates that you publish your CHM files with. Here is a step-by-step instruction:

  • If you publish CHM with a skin, open the skin file in Help+Manual
  • If you publish without a skin, open the help project in Help+Manual
  • In the Project Explorer, navigate to Configuration > HTML Page Templates > Default
  • Switch to the HTML source code tab
  • Locate the line with “X-UA-Compatible” in the HTML code editor
  • Change it to “IE=9” or “IE=edge
  • Publish your CHM file again

Old:

Modified:

 

This modification will be part of the next update of Help+Manual. However, your customized skins will need a manual tweak though – just follow the steps described above.

No Comments

Qt Help Format Support

We are happy to announce the immediate availability of QtHelpConverter, an add-on application for Help+Manual to create Qt Help files. With QtHelpConverter as add-on, Help+Manual now publishes help files in Qt Help format.

About Qt
Qt is a cross-platform application framework for developing application software that can be run on various software and hardware platforms.

Converts HTML Help to Qt Help

QtHelpConverter takes a compiled HTML Help/CHM file and outputs Qt help (.qch). Note that this application is not an authoring tool, it just converts a finished CHM help file to a corresponding Qt help file.

The converter is a stand-alone application and can be used with any standards-compliant HTML Help/CHM file.

For seamless integration in Help+Manual, QtHelpConverter has a command line interface to turn a CHM files created by Help+Manual into a Qt Help file. The converter application includes online help (in Qt format, of course) with detailed instructions.

QtHelpConverter is free

Download QtHelpConverter

 

 

No Comments

Help+Manual 7.3.1 Maintenance Update

We just released a maintenance update for Help+Manual 7.3,1. This maintenenance update fixes a few bugs that were still present in the 7.3.0 release.

Known Issues

  • Topic editor, paragraph options: if the options “Keep para with next” was set manually for a paragraph, the modification was not stored.
  • Optical glitch in Paragraph ribbon tab: for a paragraph with justified text, both options the “Left align” and “Justify” were displayed as “on”.
  • PDF/Print: 8-bit PNG images with bit-transparent areas appeared too transparent in PDF (transparency was applied by transparency-color, not by bit mask).
  • TidyXML: the batch change option included the reference to the schema file without a relative path. This is uncritical in Help+Manual but external validation of topic XML files might not work in this case.

Download

Please download the update to Help+Manual 7.3.1 from our download page and install over your existing installation of Help+Manual.

No Comments

Help+Manual 7.3 with TidyXML Released

We are happy to announce the release of Help+Manual 7.3. This maintenenance update includes an important new feature called TidyXML – a more streamlined XML topic format, that will help external translations of the content. The new TidyXML feature is explained in details here.

This update is free for all 7.xx users. Plus, there is an important update for the Premium Pack to version 3.30!

New Features

  • TidyXML implemented (see above).
  • Project Report: Remove Unused Images option implemented. When running the “Full Project Report”, it displays a list of apparently unused images. There is a new button per image folder to move these images to a backup folder.
  • AuthorIT Import: embedded images are now supported.
  • PDF: new option implemented to embed TrueType collections as Type3 fonts. TrueType collections are multiple fonts in one font file and cannot be embedded as TrueType (example: “MS Gothic”).
  • Syntax highlighter configuration dialog: option to save/load a configuration added.
  • Insert Link dialog box: when editing Internet Links, the dialog behaves more intelligently.
  • The function Rescue Copy has been moved from backstage view to the “Save As” function.
  • Style combo, Font and Font Size combobox: dropdown lists have been made longer.

Known Issues

  • Webhelp: XSS vulnerability fixed – all skins and default settings now handle direct context sensitive calls extremely strict, to prevent any form of cross-site scripting.
  • Improvements for high-res 4K monitors
  • PDF/Print: some rare line break problems fixed. Improved widow/orphan control at the beginning of topics.
  • PDF: PNG images with < 24 Bit color depth in PDF: these images were not transparent in the PDF file.
  • Word/DOCX: page breaks at the beginning of a topic are now placed before the topic heading and not between heading and text.
  • Word/DOCX: Several Wingdings bullets symbols did not work on non-ANSI Windows (e.g. Hebrew, Polish, Chinese, Russian).
  • Word/DOCX: links to topic names longer than 43 characters did not work.
  • Word/DOCX: an empty topic body was exported as 1 blank line, which is now suppressed (similar to PDF).
  • PDF Manual Designer: pasting a topic text placeholder somewhere else but at the topic band caused an error.
  • When changing a topic ID, references in secondary TOCs were not changed.
  • Bullet symbols on Hebrew Windows: Wingdings #250 did not work.
  • Image maps in responsive images with % width of page: optical glitch fixed, the hotspots had a small vertical offset.
  • XSLT style sheet for XML file rendering in browser: small bug fix for image search path – a relative image search path that was outside the project folder was not correctly resolved.
  • Webhelp: inline videos (MP4) were reset when clicked twice. A second click must stop the video instead of restarting it.
  • Insert Picture dialog: the padding window has improved positioning on small screens. The dialog now remembers alignment, HTML class, zoom and padding for new images.
  • HTML Help/CHM: Optical glitches in standard CHM-skins fixed.
  • Webhelp: when a blank line contained exactly 2 blanks, the line was exported as
    <p><span> </span></p>, which caused most browsers to ignore the line completely.

 

Premium Pack 3.3 Update

Together with Help+Manual 7.3 we have also released version 3.30 of the Premium Pack add-on. This update brings a major improvement to the Premium Pack Toolbox utility, adding a powerful new feature called Normalize Project Styles. This new tool can save you many hours of manual work when importing formatted text from HTML and CHM. See the Toolbox Help for details.

Version 3.30 of Toolbox also includes a feature for transferring your personal configuration from an old skin to a new one. You can select from ten different settings groups with previews to copy exactly what you need to an updated skin.

In a maintenance update to the skins themselves, a number of issues reported by users have been corrected. The formatting of drop-down menus in the CHM skins has been improved. All WebHelp skins now have an option for removing the “Score/Hits” line below each search result.

Download

Please download the update to Help+Manual 7.3 from our download page and install over your existing installation of Help+Manual.

No Comments

New Rescue Copy Feature in Help+Manual 7.3

In Help+Manual 7.3 we have removed the feature Rescue Copy from the Save menu. Instead, the feature is now implicitely integrated in the Save-As command. If you ever wondered what the Rescue Copy actually did, this topic is for you.

What the Rescue Copy did, was to create a new empty project that contained only the changes you made since you hit “Save” the last time. The idea was to save pending changes somewhere if Help+Manual could not save them to the original project.

Imagine you are running Help+Manual on your computer and open a help project from a remote file server. The server is connected through VPN and the connection depends on your Internet connection. The Internet connection breaks at some time, but you don’t notice because you are busy making changes to the project. Just when you hit “Save”… ooops! Can’t do it, Sir.

If the connection to the server is broken, Help+Manual cannot save the project to the original location. If you try, you get an error message.

(A bit of panik sets in…)

But Help+Manual suggests to save the project locally instead, using the Save-As command. Excellent idea, you say to yourself and hit Save-As…

The problem is: a “Save-As” normally creates a full copy of the original project, just saved locally. The entire content of the original project is duplicated in this case, including those topic files (on the file server) that have not been even loaded yet, because you did neither view nor change them. To do a complete Save-As, Help+Manual must load those yet-not-loaded files from the server to save them locally to the new project. Which, of course, fails if the server connection is broken, resulting in a second error message, that Save-As could not be completed.

(Tense panic now…)

At this point, it was time for the Rescue Copy. If nothing else works, the Rescue Copy would save the pending changes to a new help project to store them for later, when the connection to the server would be reestablished.

Would you have ever thought of this feature in Help+Manual, when in panic? Probably not. And this is exactly, why we removed the Rescue Copy feature. We implicitly implemented it in Save-As instead.

With Help+Manual 7.3, when the original Save operation cannot complete, because a server connection is broken, you can always use Save-As. Help+Manual will try to create a complete copy of the original project with Save-As.

If a complete copy is not possible (connection broken, remember!), it will save just the changes you made in the meantime and will report, what it could save and what it couldn’t. It is now a transparent save operation, that will work in any case and at the very least rescue all your recent work on the project.

No Comments

A great example of integrated WebHelp from Scooter Software

We recently worked with Scooter Software to better integrate their online help into their website.

Scooter makes BeyondCompare, the best multi-file comparison tool on the market. We use BeyondCompare ourselves to synchronize and merge source code changes and Scooter uses Help+Manual for producing their own documentation.

A WebHelp version of BeyondCompare’s documentation is also available online. The old version didn’t match their beautiful Steampunk theme, which we really love. That was a pity, because Help+Manual is extremely powerful when it comes to embedding help content into your website.

This has changed in their gorgeous new version, however: Starting with a draft of a new WebHelp skin that matches the design of their web pages, the web designers at Scooter then fine-tuned the skin and fully integrated it in the host pages. The result is a beautiful example of what is possible with Help+Manual with just a little extra tweaking:

http://www.scootersoftware.com/v4help/

Scooter Software Webhelp

 

,

No Comments

Free Trial: Premium Pack Toolbox with Normalize Styles

The Toolbox application included with the Premium Pack skin suite is a Swiss Army knife for Help+Manual projects and skins as well as a configuration utility for the Premium Pack skins. The upcoming 3.23 version of Toolbox has a powerful new feature called Normalize Styles that can radically accelerate two important tasks:

  • Integrating content imported from HTML and CHM files into your project stylesheet
  • Removing inline/manual formatting to clean up your projects’ XML source for translation

This is already fully compatible with the new Tidy XML feature in the upcoming Help+Manual 7.3 update, so if you are already using the 7.3 beta you can use the latest version of Toolbox with it. You can download a free trial version of Toolbox with these features here and try it out before it is officially released with Premium Pack 3.23:

Premium Pack Toolbox Free Trial

If you are a registered Premium Pack user you can use the trial version without restrictions. Otherwise you can test it on Help+Manual projects with a maximum of 20 topics. The trial will not disable your current version of Toolbox if you have one and expires two weeks after installation.

Integrating imported HTML into your stylesheet

When you import HTML files or a CHM help file to a Help+Manual project your formatting comes in as inline or “manual” formatting that cannot be directly controlled by the styles in your project. Normally, you need to create styles based on the formatting and then manually apply them to all the paragraphs in your project where you want to use the style.

So long as the text imported from HTML or CHM is tagged with style names, Normalize Styles eliminates many hours of tedious work by doing this automatically. All you need is for a paragraph or any text within the paragraph to be tagged with a style name. It will then apply your selected paragraph style to the entire paragraph. At the same time it eliminates manual formatting so that your paragraphs are fully under the control of the project stylesheet. But it also optionally allows you to keep text already formatted with other styles and manual bold, italics and underlining. And you can also automatically apply specified styles to hyperlinks and toggle links.

 

Normalize entire project

The second tab of the Normalize Project Styles tool is called “Entire Project”. It automatically normalizes all the text in your entire project, removing manual formatting and putting everything under the control of the styles defined in your project stylesheet. This can be very useful when you are preparing your project for translation, because it significantly reduces the number of redundant inline XML tags and attributes that can make life more difficult for the translator.

This even applies if you are using the new Tidy XML feature introduced in Help+Manual 7.3, because your project may still contain a lot of manual formatting “cruft” accumulated during normal day-to-day work (and it is fully compatible with Tidy XML). In our tests, Normalize reduced the tag volume in a 750-topic project by a further 25%, even after Tidy XML had been applied.

If you use styles systematically, this function too can save you hours of tedious work because you no longer need to manually tidy up all the manually-formatted paragraphs in your project after locating them with Project Report. And here too, you can protect text already formatted with other styles and manual bold, underline and italics.

No Comments

Help+Manual 7.3 Beta with TidyXML

We are glad to announce that Help+Manual 7.3 Public Beta is available for download! Version 7.3 implements a slightly modified XML format that is more translation-friendly. We had announced this feature before, now you can try it for the first time.

You can download and install the 7.3 beta version like any previous 7.x update from this direct link:

http://download.ec-software.com/help-and-manual-setup-v730-beta.exe

The link will be kept active during the beta phase and will be updated 2 or 3 times a week.

 

About TidyXML

As you know, Help+Manual saves a project in XML format, enabling external translation programs to parse the XML and translate it. The XML code, that Help+Manual creates, however, is a bit more complicated than many translation programs would like to have it. It is best explained with an example…

Please run Help+Manual and paste the following 2 lines of text into a topic:

Now let’s switch the editor to “XML View” and have a look at the XML code created for these 2 lines:

 

The XML colored in yellow is the code created for the two lines. These are 2 paragraphs (<para> tags in XML) and several separate text elements (<text> tags in XML). A translation program that parses the XML code, does not see the visual representation like you do in Help+Manual. It sees the XML structure only and has to make sense of it.

 

Changing the XML format

Version 7.3 has a switch that you can activate to apply a new and cleaner (tidier) XML syntax. The switch applies per help project and is placed under Configuration > Common Properties > Miscellaneous Options.

To activate the function, perform the following steps:

  1. Make a backup of your help project (!)
  2. Make sure the backup can be restored any time
  3. Open the help project and navigate to the configuration section as shown below
  4. Enabe the option “Write translation-friendly XML“, then click “Apply to all topics

 

 

The difference in XML

The new XML syntax writes <text> tags only where necessary. If the text style is identical with the paragraph style, the text is simply placed between the <para>…</para> tags, making it much easier to read for an external translator. Explicit <text> tags are inserted if the text has a different format than the paragraph. Furthermore, style classes are inherited. The new XML syntax omits redundant “styleclass” attributes for <text> tags and links.

The entire XML structure becomes smaller and more readable.

This new XML structure, however, is not compatbile with older versions of Help+Manual. While you won’t lose content when opening such a converted help project with an older version of H&M, the style inheritance is not recognized and the format might look distorted. Do not open a converted project with an older version of Help+Manual!

 

No Comments

Using Help+Manual WebHelp on MS Azure

Experienced Help+Manual user Garry Robinson has just published a terrific tutorial explaining how he deploys and maintains Help+Manual WebHelp documentation on Microsoft Azure sites. In addition to the basics, he also explains how Dropbox and other similar services can be used to keep the site up to date.

Garry reports that the performance is outstanding, even with the lowest-tier Azure web service that he is using.

Visit the tutorial here:

https://www.linkedin.com/pulse/publishing-websites-azure-garry-robinson

Azure website configuration

 

No Comments