Version 1.1.1 - Fixed: internal version-string drift

Maintenance release.

• Fixed internal version-string drift: the plugin header correctly read 1.1.0, but four other version references (the admin CSS enqueue cache-bust parameter, both JS enqueue cache-bust parameters, and the GitHub updater's fallback default) had been left at 1.1.1 from an internal build and were never brought back down to match. All version strings are now consistent at 1.1.1.
• No functional or output changes to the conversion engine itself; this release only corrects asset cache-busting and update-check metadata.

Full Changelog: v1.1.0...v1.1.1

Version 1.1.0 - Layout-fidelity release

Layout-fidelity release.

• Tab characters (w:tab) no longer collapse into a single space in the rendered page. Multiple tab-stopped words on one line (e.g. TIME = 3 HOURS [tabs] FULL MARK = 100) were being crushed together at the left edge, because HTML collapses runs of literal tab/space whitespace by default. Tabs are now rendered with non-collapsing spacing so the intended separation survives.
• Images anchored with text-wrap in Word (wp:anchor + wrap-square/tight/through, aligned left or right) are now inserted with WordPress's native alignleft/alignright/aligncenter class, so the surrounding paragraph text wraps around the image as it did in the source document. Inline images and images set to "top and bottom" wrapping are unaffected.
  Correctness patch.
• Fixed: images anchored with text-wrap in Word were still being inserted without their alignleft/alignright/aligncenter class. The class was computed correctly and even showed up in the plugin's own Preview tab, but the actual "Insert into editor" step built its own attributes for the uploaded media (src, wp-image-*) as a separate object that was merged in afterwards, silently overwriting the alignment class rather than combining with it. Both classes are now combined so the published post wraps text around the image exactly as it did in v1.1.0's Preview.
• Hardened tab-stop handling: tabs are now kept as a real tab character wrapped in white-space: pre, rather than a fixed-width non-breaking-space substitute. This is closer to the source document's actual semantics and is more resistant to rich-text editors renormalizing plain whitespace text on a later manual edit.

Full Changelog: v1.0.0...v1.1.0

v1.0.0 – First Stable Release: Mec-Docx-Converter

This is the first stable release of the MEC DOCX Converter plugin.

The plugin provides a direct bridge between .docx documents (from Microsoft Word, Google Docs, and LibreOffice) and the WordPress editor. It converts semantically structured content into clean, theme‑compatible HTML, stripping out inline presentation styles (fonts, sizes, colours, and alignment) by default.

Key Features

• Semantic HTML Mapping – Word headings (Heading 1–6) map to <h1>–<h6>, lists to <ul>/<ol>, quotes to <blockquote>, and tables to <table> with proper <thead>/<tbody> structures. Inline presentation is deliberately omitted to ensure theme compatibility.

• Rich Text Preservation – Bold, italic, underline, strikethrough, subscript, superscript, and highlighted text (<mark>) are all correctly converted.

• Media Library Integration – Images are extracted from the document, uploaded to the WordPress media library, and inserted with the correct src, alt text, and wp-image-* classes.

• Complex Structure Support – Nested lists (up to 5 levels), table colspan/rowspan, footnotes/endnotes with back‑links, and checkboxes are fully supported.

• Editor Compatibility – Works with both the Gutenberg editor (inserts as a Classic block) and the Classic Editor, including CKEditor and TinyMCE environments.

• Automatic Updates – A built‑in GitHub update checker queries the repository API (cached for 12 hours) and enables one‑click updates directly from the WordPress admin panel.

Installation

1. Upload the plugin folder to /wp-content/plugins/ or install via the WordPress repository.
2. Activate the plugin from the Plugins menu.
3. When editing a post or page, locate the MEC DOCX Converter meta box.
4. Select a .docx file, preview the conversion (Visual/Raw HTML tabs), and click Insert into editor.

Customisation

Advanced users can embed custom style maps inside the .docx file to map specific Word styles to arbitrary HTML tags and classes, giving full control over the output markup.

Feedback & Contributions

Issues, feature requests, and pull requests are managed through the GitHub repository issue tracker.