Skip to content

New Context Menu and Options and Bug Fixes
Compare
Choose a tag to compare
@RickStrahl RickStrahl released this 01 Sep 18:46
· 239 commits to main since this release
1.5.12
058fdb4

  • Updated Editor Context Menu
    The Editor's context menu has been updated to forward all menu handling to WPF rather than HTML based menu display. Currently the new menu handles Copy/Cut/Paste and spellchecking duties only, but additional menu options/features can now be added more easily.

  • Edit in Image Editor Context Menu
    You can now right click over an image embedded into a Markdown document and use the Context menu to select Edit in Image Editor to open the document for editing in your configured image editor.

  • Edit Image Link Context Menu
    You can now hover over an image embedded in Markdown and use Edit Image Link to reopen the image in the Image Embedding Dialog.

  • Copy Selection as HTML now formats Clipboard as HTML Data Type
    You can now use Copy as HTML from the Edit or Context menus to export your Markdown selections to HTML (as before). In addition the new behavior adds the text using HTML Clipboard formatting so you can more easily paste the HTML into rich text editors (like Outlook or Gmail's editor for example) with formatting intact. Text editors still see the raw HTML output.

  • Support for Pandoc YAML headers ending in ...*
    Thanks to a fix in the Markdig Pandoc parser, Pandoc alternate style YAML headers that end in ... rather than --- are now stripped from rendered Markdown output. Additional adjustments for spellcheck exclusions and Weblog Publishing are forthcoming in future updates.

  • Fix: Addin Markdown Parsers now are selectable immediately
    When installing an addin that exposes a new Markdown Parser is now visible and selectable immediately from the Markdown parser selection drop down on the toolbar.

  • Fix: Pandoc Addin FrontMatter Support Change
    The Pandoc Addin now handles YAML FrontMatter using Pandoc's native rendering, which works differently than the default Markdig parser. Pandoc picks out the title property from the YAML and automatically injects a <h1> tag with the title into the document which is not the case with the default Markdig parser. The reason for the change is to ensure you get to see the raw Pandoc output that you will see if the document is explicitly run through Pandoc.

Assets 2
Loading