If you’re using chrome desktop then you can use Ctrl+Shift+V to paste as plain text instead of notepad.
Also in the admin site settings page, you can disable this fancy pasting behavior by unchecking the “enable rich text paste” option.
2 לייקים
Thanks, but my goal is to keep the original formatting from microsoft word (in the raw data), not strip it down to plain text.
Currently, Discourse removes a variety of the formatting–such as font size and font type, while leaving others (bold and italics seem to stay there). As a comparison, Gmail composer seems to leave all formatting.
To try to keep more formatting, I suppose an alternative would be to upload a word document (not paste in text to the composer–but upload the actual doc). The problem there, I think, is that discourse does not show the contents of the upload inline (it just displays an upload link).
Then paste the raw HTML.
There are different goals involved. Gmail’s goal is to preserve all the formatting, whereas a forum’s goal is to keep a meaningful subset of it while preventing abuse (huge text, blinking text, OVERLY LARGE FONTS, annoying colours, etc.)
As a simple example, here is some simple text’s HTML as generated by Office, present in the clipboard as text/html:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8"/>
<title></title>
<meta name="generator" content="LibreOffice 7.1.2.2 (Linux)"/>
<style type="text/css">
@page { size: 21.59cm 27.94cm; margin: 2cm }
p { margin-bottom: 0.25cm; line-height: 115%; background: transparent }
</style>
</head>
<body lang="en-CA" link="#000080" vlink="#800000" dir="ltr"><p style="margin-bottom: 0cm; line-height: 100%">
<b>Hello there</b><span style="font-weight: normal"> sunshine </span><i><span style="font-weight: normal">eh</span></i></p>
</body>
</html>
It looks like:
@page { size: 21.59cm 27.94cm; margin: 2cm } p { margin-bottom: 0.25cm; line-height: 115%; background: transparent }Hello there sunshine eh
But when interpreted by to-markdown.js you get:
**Hello there** sunshine *eh*
Hello there sunshine eh
You cannot, unless you put it there yourself as I did in this post. If you really need it there, hide it in a comment. If you want to later convert it yourself to markdown, use something like pandoc.
2 לייקים
I support transferring to markdown on the post that is displayed to others for some consistency. It’s the raw entry I’m curious about.
How do you get the raw html of a word doc that you could paste in?
Save it as HTML from Word, or copy it to the clipboard and pull the text/html explicitly from the clipboard.
4 לייקים
If all you care about is being able to reference the raw input at a later point, this component might work for you.
It adds a button to the post menu that shows the raw content on a per-post basis.
5 לייקים
@jomaxro, what is the syntax for the raw markup of a comment?
What are you asking for? Are you asking what markdown is? Like https://commonmark.org/ Are you asking how to get the raw markdown for a post? Like /raw/123
For a single post, you can add the ID to the URL. For example, when I share your post, the link is https://meta.discourse.org/t/get-back-the-real-raw-data-that-created-a-post/189183/27, and https://meta.discourse.org/raw/189183/27 is the raw version of your reply.
2 לייקים
@jomaxro, /raw/ doesn’t work at any of discuss.kde.org/c/community/blogs/24’s posts, for, at view-source:discuss.kde.org/raw/43656, I observe:
<pre>Konqi | 2026-01-23 22:43:37 UTC | #1
<p>Leaking memory is impolite. It’s messy, it can suggest logic bugs, and thanks to AI grifters RAM is expensive.
</p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://nicolasfella.de/posts/detecting-leaks-in-kde-ci/?utm_source=atom_feed">https://nicolasfella.de/posts/detecting-leaks-in-kde-ci/?utm_source=atom_feed</a></small>
-------------------------
</pre>
…whereas, when the details is interactively expanded at discuss.kde.org/t/43656, I can expand it to:
Can this be feasibly catered for on upstream Discourse’s end? I’ve observed similar at other, slightly-customised Discourse instances, which is why I ask.
What problem are you trying to solve?
Those topics are special because they are links to big posts.
That is the raw text of the op.
לייק 1
The raw text of the OP in that topic is:
○ → curl https://discuss.kde.org/posts/132565/raw
<p>Leaking memory is impolite. It’s messy, it can suggest logic bugs, and thanks to AI grifters RAM is expensive.
</p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://nicolasfella.de/posts/detecting-leaks-in-kde-ci/?utm_source=atom_feed">https://nicolasfella.de/posts/detecting-leaks-in-kde-ci/?utm_source=atom_feed</a></small>
This is exactly what is rendered in the cooked version.
It’s not a details block being expanded. A click on Show Full Post loads something else, which is the full expansion of the embed, which does not come from the post raw but from additional post metadata.
You can see the network request in your browser when you click on it, here’s the equivalent:
○ → curl -s -H 'accept: application/json' 'https://discuss.kde.org/posts/132565/expand-embed' | jq -r .cooked
<div><div>
<p>Leaking memory is impolite. It’s messy, it can suggest logic bugs, and thanks to AI grifters RAM is expensive.</p>
…
…
…
<p>LSAN is now enabled for some Frameworks CI builds, but ideally it would be enabled for all KDE projects. And of course any leaks found along the way should be fixed.</p>
<p>Happy leak-fixing!</p>
</div></div>
<hr>
<small>This is a companion discussion topic for the original entry at <a href='https://nicolasfella.de/posts/detecting-leaks-in-kde-ci/?utm_source=atom_feed'>https://nicolasfella.de/posts/detecting-leaks-in-kde-ci/?utm_source=atom_feed</a></small>
Did you want to see the contents of the embed? If so, use the above. If not, what are you expecting to see?
2 לייקים
@supermathie, indeed. Many thanks! Evidently, much more of the Discourse API exists than I’m aware of.
לייק 1