docs: prepare bilingual MoleditPy 5 stable security and installer guidance
Assisted-by: GPT-6.1 Sol
docs: remove temporary alpha installation advice
Assisted-by: GPT-6.1 Sol
Make bilingual alpha installation instructions match published packages
Assisted-by: GPT-6.1 Sol
Synchronize bilingual MoleditPy 5 migration documentation
Document PySide6, Python 3.9-3.14, RDKit/Direct conversion, LGPL core and independent plugin licensing, and process-local Qt binding selection.
Assisted-by: GPT-6.1 Sol
docs: align molecule examples and remove superseded screenshots
Assisted-by: GPT-6.1 Sol
docs: simplify wiki installation to two commands
Assisted-by: GPT-6.1 Sol
docs: expand bilingual wiki with illustrated workflows
Assisted-by: GPT-6.1 Sol
Say it is plugins that fail on the macOS certificate problem
MoleditPy itself works without the root certificates; what fails is the
plugins that connect to the internet (Plugin Installer, PubChem lookups,
AI chat). The symptom text now says that and quotes the message users
actually see, "[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify
failed", instead of the full traceback line.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add "Installing Python and pip" (EN/JP)
A page for users without a working Python: installing Python and pip
on Windows, macOS and Linux, then pointing on to the platform pages.
Its troubleshooting section covers the macOS problem users keep hitting:
the python.org installer leaves Python without root certificates, so pip
works (it ships its own bundle) but the Plugin Installer, PubChem
lookups and other online features fail with CERTIFICATE_VERIFY_FAILED
until Install Certificates.command is run. It also covers proxies,
"pip not found", externally-managed-environment, and picking a Python
version.
Linked from Home, both Troubleshooting pages, and the opening of every
platform installation page; the macOS pages also mention the
certificate step directly.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add YouTube video links
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
docs: move What You Can Do with Plugins guide to moleditpy-plugins.wiki
Remove What-You-Can-Do-with-Plugins (.md and -JP.md) from the main app
wiki and update Home.md and Using-Plugins navigation to point directly
to the authoritative plugin wiki pages at moleditpy-plugins.wiki.
Co-Authored-By: Gemini 3.8 Flash <noreply@google.com>
docs: add comprehensive what-you-can-do-with-plugins guide in English and Japanese
Includes:
- Part I: 6 typical end-to-end use cases and recommended plugin toolchains
- Part II: Comprehensive problem-solution matrix covering all 78 official plugins across 11 categories
- Cross-links from Home, Using-Plugins, and Japanese counterparts
Assisted-by: Gemini 3.8 Flash
docs: add Japanese installation pages for Windows, macOS and Linux
Docker was the only installation page with a JP counterpart, so Japanese
readers hit English for the three platform installs the wiki actually
recommends. Translate all three, list them on Home, and repoint the
existing JP pages (and Docker-JP) at the JP versions.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Move plugin pages to the plugins wiki; rebuild the index
The per-plugin guides and the catalogue documented moleditpy-plugins, not the
editor, so they now live in that repository's own wiki and this Home page
links to it. Using Plugins stays here: it is about the plugin system, which is
part of the application rather than any particular plugin.
Home.md now indexes every page in the wiki, including the ones added
yesterday that were never linked (Keyboard Shortcuts, File Formats,
Command-Line Options, Using Plugins, Troubleshooting), and marks which pages
have a Japanese counterpart.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>