[feature] Export to Word Enhanced - sanitize generated comment

[radzrader]

I was having a look at the fingerprint coming from these docs and noted that python-docx adds "generated by python-docx".

Having a deeper look I have added to my local version a sanitize method however you could also now add the current user as the author or set the title for example (line 1525), I added self._sanitize_metadata(doc):

        """
        Convert Markdown text to Word document
        Supports: headings, paragraphs, bold, italic, code blocks, lists, tables, links
        Additionally: Mermaid fenced blocks (```mermaid) rendered client-side via Mermaid.js (SVG+PNG),
        LaTeX math to Word equations, and OpenWebUI citations to References.
        """
        doc = Document()
        self._sanitize_metadata(doc)
        self._active_doc = doc

then at the very end:

    def _sanitize_metadata(self, doc: Document):
        """Removes library fingerprints and sets professional defaults."""
        p = doc.core_properties
        p.author = ""  # Set your preferred author name
        p.comments = ""  # Clears any default library comments
        p.title = ""  # Initialise as empty; logic fills this later
        p.keywords = ""
        p.subject = ""

        try:
            from docx.opc.constants import CONTENT_TYPE as CT

            # Setting these to an empty string or a custom value
            # obscures the default 'python-docx' signature.
            p.category = ""
            p.content_status = ""
        except Exception:
            pass

[Fu-Jie]

This has been implemented in v0.5.0! 🎉

The plugin now includes a _sanitize_metadata() method that:

• Clears author, last_modified_by, title, comments, keywords, subject, category, and content_status from the default python-docx fingerprints
• Sets author and last_modified_by to the real OpenWebUI user name
• Sets title to the chat title (or extracted Markdown heading as fallback)

No more "generated by python-docx" leaking into document properties — exactly what you proposed. Thanks for the detailed suggestion, it helped shape the implementation!

Update the plugin to get this fix. If you find this helpful, a star on openwebui-extensions would be much appreciated! ⭐