1.0.1

Settings are now searchable on Obsidian 1.13 and later.

The settings tab declares its options through the declarative settings API, so they appear in Obsidian's settings search and are indexed by the framework. On Obsidian 1.4–1.12 the tab keeps rendering the same options as before; minAppVersion is unchanged at 1.4.0.

Also in this version:

• The empty-Language fallback moved to where the value is read, so an emptied field can no longer reach the compiler as Language= in the project file.
• The wide-input styling is scoped to the settings controls rather than to a class the old rendering added, so it now applies on both renderings.

Install

Download main.js, manifest.json and styles.css into <vault>/.obsidian/plugins/md-to-chm/, then enable the plugin in Settings → Community plugins. Requires HTML Help Workshop's hhc.exe — see the README.

1.0.0

Export Obsidian notes, with their attachments, into a single offline Compiled HTML Help (.chm) file.

Install

1. Download main.js, manifest.json and styles.css from the assets below.
2. Put all three in <vault>/.obsidian/plugins/md-to-chm/.
3. Reload Obsidian, then enable Markdown to CHM under Settings → Community plugins.

Requirements

• Windows — the plugin drives hhc.exe from HTML Help Workshop, which is not bundled (Microsoft no longer distributes it; the README links a copy that still works). The settings tab detects the compiler and has a Test compiler button.
• Desktop only. Obsidian 1.4.0 or later.

What it does

• Export the current note, a selection, or a folder subtree.
• Per-export table of contents: heading hierarchy, folder structure, or a flat list.
• Optional keyword index built from note tags and aliases.
• Attachments are copied into the CHM and links rewritten, so internal note links navigate inside the finished file.
• Builds are staged in a temp directory with sanitized names, which is what keeps hhc.exe working when your vault path contains spaces or dot-folders.

Fixed in this build

• Images and other media are read out of Obsidian's resource URLs, including the app://<token>/<absolute path> form, so attachments are embedded instead of silently dropped.
• Plain relative image paths are resolved against the note that wrote them.
• Media that cannot be found is reported, as is an export with attachments switched off, or a destination file still locked by the CHM viewer.