{"id":16277,"date":"2018-09-25T09:30:53","date_gmt":"2018-09-25T16:30:53","guid":{"rendered":"https:\/\/www.sapien.com\/blog\/?p=16277"},"modified":"2018-09-25T09:05:47","modified_gmt":"2018-09-25T16:05:47","slug":"powershell-helpwriter-2018-service-release-v2-2-41","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2018\/09\/25\/powershell-helpwriter-2018-service-release-v2-2-41\/","title":{"rendered":"PowerShell HelpWriter 2018: Service Release v2.2.41"},"content":{"rendered":"

We released a new service build of PowerShell HelpWriter 2018 (v2.2.41). This service build is included as part of the regular update cycle for our subscribers.<\/p>\n

 <\/p>\n

New Features<\/h2>\n

This service release introduces the new spell checking feature for the help file designer.<\/p>\n

\"Spell<\/a><\/p>\n

 <\/p>\n

 <\/p>\n

Spell Checker<\/h3>\n

PowerShell HelpWriter now has a built-in spell checker for the help designer. The spell checker will draw a red squiggly line under spelling errors:<\/p>\n

\"Red<\/a><\/p>\n

Note: The real-time spell checker is limited to the active field within the designer.<\/em><\/p><\/blockquote>\n

 <\/p>\n

Use the context menu to get suggestions for the spelling error:<\/p>\n

\"Suggested<\/a><\/p>\n

 <\/p>\n

You can manually trigger spell checking by pressing the Spell Check<\/strong> button from Ribbon > Home > Edit.<\/p>\n

\"Spell<\/a><\/p>\n

Note: This command will trigger spell check for all applicable fields in the current view of the designer.<\/em><\/p><\/blockquote>\n

 <\/p>\n

You can also trigger spell checking for the corresponding field by using the text field\u2019s context menu:<\/p>\n

\"Spell<\/a><\/p>\n

 <\/p>\n

Spelling Suggestions Dialog<\/h4>\n

Whenever you trigger a manual spell check, PowerShell HelpWriter presents you with a suggestion dialog for potential spelling mistakes:<\/p>\n

\"Spell<\/a><\/p>\n

 <\/p>\n

You can use this dialog to temporarily ignore the word or replace it with a provided suggestion. You can use the Add<\/strong> button to add the word to the Custom Dictionary<\/strong> (see below) so that it will no longer be flagged as a misspelled word.<\/p>\n

The Options\u2026<\/strong> button displays the following Spelling Options dialog:<\/p>\n

\"Spell<\/a><\/p>\n

 <\/p>\n

This dialog provides an alternative way of modifying the spell checker\u2019s options. The spelling options are covered below.<\/p>\n

 <\/p>\n

Where is Spell Checking Supported?<\/h4>\n

The designer limits spell checking to the Synopsis<\/em>, Description<\/em> and Note<\/em>s \/ Remarks<\/em>\u00a0fields. Therefore, fields such as the Name, Type, <\/em>and\u00a0Code<\/em> fields will be excluded.<\/p>\n

In addition, spell checking is not available for About help files at this time.<\/p>\n

 <\/p>\n

Supported Languages<\/h4>\n
<\/h5>\n

PowerShell Helpwriter is capable of supporting multiple languages. Out-of-the-box, PowerShell Helpwriter supports the following languages:<\/p>\n

    \n
  1. English (US)<\/li>\n
  2. Spanish (Spain)<\/li>\n<\/ol>\n

     <\/p>\n

    Spelling Options<\/h4>\n

    You can configure the Spell Checker\u2019s settings in Options > Spelling:<\/p>\n

    \"Spelling<\/a><\/p>\n

    <\/h5>\n

     <\/p>\n

    General Settings<\/h5>\n

    Enable real-time spell checking<\/strong><\/p>\n

    Check this option to enable real-time spell checking as you type. When enabled, spelling errors are underlined with a red squiggly line.<\/p>\n

     <\/p>\n

    Detect language from document directory<\/strong><\/p>\n

    PowerShell help files are normally located in a language specific folder:<\/p>\n

    \"Language<\/p>\n

    Note: The folder name is using the language tag name declared by <\/em>National Language Support (NLS) API Reference<\/em><\/a> at the Go Global Developer Center.<\/em><\/p><\/blockquote>\n

    When this option is enabled, PowerShell HelpWriter will automatically select that language of the spell checker depending on the name of the parent folder of the help document. If PowerShell HelpWriter is unable to determine the language, or if the language isn\u2019t supported by the spell checker, it will then use the default language.<\/p>\n

     <\/p>\n

    For example, the files located in the es-ES<\/em> folder will use the Spanish dictionary for spell checking:<\/p>\n

    \"Spell<\/a><\/p>\n

     <\/p>\n

    Default Language<\/strong><\/p>\n

    This option allows you to choose which language to use as the default setting for spell checking.<\/p>\n

     <\/p>\n

    Ignore Settings<\/h5>\n

    These settings control the behavior of the spell checker by specifying in which cases the spell checker should ignore a potential spelling error.<\/p>\n

     <\/p>\n

    Edit Custom Dictionary<\/h5>\n

    Use the Edit…<\/strong> button to edit the contents of the Custom Dictionary<\/strong> (see below).<\/p>\n

     <\/p>\n

    Custom Dictionary<\/h4>\n

    PowerShell HelpWriter supports a customizable dictionary which allows you to add words to the spell checker that would otherwise be flagged as misspelled because they are not included in the preset dictionary.<\/p>\n

    \"Custom<\/a><\/p>\n

     <\/p>\n

    PowerShell HelpWriter\u2019s default Custom Dictionary<\/strong> comes prepopulated with PowerShell keywords.<\/p>\n

     <\/p>\n

     <\/p>\n

    Project Panel \u2013 Multi-File Selection<\/h3>\n

    The Project panel now allows you to selected multiple files at once:<\/p>\n

    \"Project<\/a><\/p>\n

     <\/p>\n

    You can use the multi-select feature to open several files at once or to bulk remove files from the project.<\/p>\n

     <\/p>\n

    File Line Endings<\/h3>\n

    You can now use PowerShell HelpWriter\u2019s status bar to view the line ending of the active file:<\/p>\n

    \"Status<\/a><\/p>\n

    To change the line ending, click on the line ending displayed in the status bar and select the desired settings from the pop-up menu:<\/p>\n

    \"Line<\/a><\/p>\n

     <\/p>\n

    You can choose from the following options:<\/p>\n\n\n\n\n\n
    Option<\/strong><\/td>\nDescription<\/strong><\/td>\nOS<\/strong><\/td>\n<\/tr>\n
    CR LF<\/td>\nCarriage Return New Line<\/td>\nWindows<\/td>\n<\/tr>\n
    LF<\/td>\nNew Line<\/td>\nUnix<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

     <\/p>\n

     <\/p>\n

    About Box \u2013 Copy Version Information<\/h3>\n

    The About Box\u2019s Copy Version Info<\/strong> button will now copy the application and OS information to the clipboard.<\/p>\n

    \"AboutBox<\/a><\/p>\n

    Use this feature to copy the relevant information for technical support on our forums:<\/p>\n

     <\/p>\n

    Product:  PowerShell HelpWriter 2018 (64 Bit)\r\nBuild:    v2.2.41\r\nOS:       Windows 10 Pro (64 Bit)\r\nBuild:    v10.0.17134.0\r\n<\/pre>\n
    <\/h2>\n
    Feedback<\/h2>\n
    Please continue providing your feedback. Many of the new features included in the service builds are suggestions from users like you. Submit your suggestions or feature requests on the Wish List and Feature Requests<\/a> forum or the new Feature Requests<\/a> page.<\/p>\n
    You can view the complete service build log here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
    We released a new service build of PowerShell HelpWriter 2018 (v2.2.41). This service build is included as part of the regular update cycle for our subscribers.   New Features This service release introduces the new spell checking feature for the help file designer.     Spell Checker PowerShell HelpWriter now has a built-in spell checker […]<\/p>\n","protected":false},"author":10,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1038,624,21,632],"tags":[28,1267,645,155,141],"class_list":["post-16277","post","type-post","status-publish","format-standard","hentry","category-powershell-helpwriter","category-service-build","category-software-news","category-whats-new-software-news","tag-powershell","tag-powershell-helpwriter-2018","tag-service-build-2","tag-service-release","tag-whats-new"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/16277","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/comments?post=16277"}],"version-history":[{"count":7,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/16277\/revisions"}],"predecessor-version":[{"id":16301,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/16277\/revisions\/16301"}],"wp:attachment":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/media?parent=16277"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/categories?post=16277"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/tags?post=16277"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}