mirror of
https://github.com/amitwh/markdown-converter.git
synced 2026-10-01 09:19:34 +05:30
amitwh
0be46d4bac
- electron-builder config moves to electron-builder.config.js so markitdown bundling is conditional per platform (PyInstaller only builds for the host OS; a missing binary now logs a warning and ships without it instead of failing the build); package.json static build section removed, all npm scripts pointed at the config; third-party-licenses/ added to packaged files - FIX (pre-existing): packaged apps looked for bundled pandoc in resources/bin, but extraFiles land next to the executable (Contents/ on macOS) — packaged builds silently fell back to system pandoc since 4.5. New bundledToolDir() resolves the real location for pandoc + markitdown - download-tools.js pins the win32 pandoc.exe SHA-256 (fetched + verified) - sharp packaging test accepts sharp 0.35's versioned binding filename - release.yml: bundle-markitdown step (best-effort) on every OS and a new macOS job; release aggregates linux+windows+macos artifacts Local release artifacts built and verified (dist/): - MarkdownConverter-4.7.0.AppImage (363MB, pandoc+markitdown bundled, packaged app boots clean, tools resolve at the fixed path) - markdown-converter_4.7.0_amd64.deb (293MB) - MarkdownConverter-Setup-4.7.0.exe (223MB), portable exe (223MB), zip (305MB) — pandoc bundled; markitdown omitted (cannot cross-build), legal docs verified inside app.asar 637/637 tests green; lint clean.
PanConverter Windows Explorer Context Menu Integration
This directory contains scripts to add PanConverter to the Windows Explorer context menu, allowing you to right-click on files and convert them directly without opening the full application.
Features
Context Menu Options
- Convert with PanConverter: Shows a format selection dialog for any supported file
- PanConverter > Convert to...: Direct conversion options (for Markdown files)
- HTML
- DOCX
- LaTeX
- PowerPoint
Supported File Types
- Markdown:
.md,.markdown - HTML:
.html,.htm - Documents:
.docx,.odt,.rtf - LaTeX:
.tex - PDF:
.pdf - Presentations:
.pptx,.ppt,.odp
Installation Methods
Method 1: Automatic (During PanConverter Installation)
When installing PanConverter using the Windows installer, you'll be prompted to install context menu integration automatically.
Method 2: Manual Installation
Using PowerShell (Recommended)
- Right-click on
install-context-menu.ps1 - Select "Run with PowerShell"
- Follow the prompts (will request administrator privileges)
Using Batch File
- Right-click on
install-context-menu.bat - Select "Run as administrator"
- Follow the prompts
Using Registry File Directly
- Right-click on
install-context-menu.reg - Select "Merge"
- Confirm the registry modification
Uninstallation
Using PowerShell
.\install-context-menu.ps1 -Uninstall
Using Batch File
Run uninstall-context-menu.bat as administrator
Using Registry File
Run uninstall-context-menu.reg
How It Works
Command Line Interface
The context menu integration works by passing command line arguments to PanConverter:
--convert <file>: Shows conversion dialog for the specified file--convert-to <format> <file>: Directly converts to the specified format
Examples
# Show conversion dialog
PanConverter.exe --convert "document.md"
# Direct conversion to PDF
PanConverter.exe --convert-to pdf "document.md"
Conversion Process
- PanConverter reads the input file
- Creates a temporary file if needed
- Uses Pandoc to convert to the target format
- Saves the output in the same directory as the input file
- Shows a Windows notification when complete
Requirements
- PanConverter must be installed in the default location:
%LOCALAPPDATA%\Programs\PanConverter\ - Pandoc must be installed and accessible from the command line
- Administrator privileges required for registry modifications
Troubleshooting
Context Menu Not Appearing
- Ensure you ran the installation script as administrator
- Try logging out and back in, or restart Windows Explorer
- Check if PanConverter is installed in the expected location
Conversion Failures
- Verify Pandoc is installed:
pandoc --version - Check if the input file is not corrupted or locked
- Ensure you have write permissions in the output directory
Permission Errors
- The installation scripts require administrator privileges to modify the registry
- If you get permission errors, right-click and "Run as administrator"
File Descriptions
install-context-menu.reg: Registry entries for context menuuninstall-context-menu.reg: Registry entries removalinstall-context-menu.ps1: PowerShell installation scriptinstall-context-menu.bat: Batch installation scriptuninstall-context-menu.bat: Batch uninstallation scriptnsis-installer.nsh: NSIS installer integration script
Security Note
The scripts modify the Windows registry to add context menu entries. Only run these scripts if you trust the source and understand the changes being made to your system.