How can formatting from websites (e.g. Etymonline and Wiktionary always contains bolds, italics, underlining, hyperlinks) be copied and pasted, or efficiently replicated? I yearn to avoid pasting only the text and then formatting myself anew.
At present, I copy and paste with the right cursor on the mouse, but then I must unproductively add * * to each italicised phrase, and ** ** to each bolded phrase. How can I improve this?
There are browser extensions that allow you to copy formatted text to the clipboard as markdown. For instance, you can use this extension on Chrome:
Here's one for Safari:
And if you're on OS X you'll want to take a look at these markdown tools:
Which provide a great deal of flexibility in converting to and from markdown from a variety of other formats and services.
It is unlikely that Stack Exchange will provide these services.
Data on the clipboard frequently has multiple types. You can see how this works when you use
Paste Special in Microsoft Word:
These data types are called MIME types, or sometimes Content-types. Here are some example text types that are defined:
The application that is receiving the paste, such as Microsoft Word or the question editing panel has to know what to do with a particular content type.
Now, consider the fact the text syntax we use (e.g.
**text**) formats text using a method called Markdown, which converts the syntax to HTML. Similarly, JIRA uses its own syntax to convert plain text to HTML formatted text.
Now, consider the problem that would be faced: when pasting, Stack Exchange would have to somehow capture the HTML formatted text and then use that to re-generate Markdown syntax, from a source that could be generated from anywhere, not just another Markdown interpreter. Can you imagine how difficult that process might be? This is especially true when you begin to consider CSS: some sites might use
<b></b> for bold, and other sites might use CSS and
<div></div> for everything, and there are still other ways to do it. HTML and CSS are, themselves, complicated programming languages, not parseable by regex.
The bottom line is, this would be a very difficult problem. Further, there is a lot of pushback against doing it in the first place (Thanks @HomegrownTomato) this will almost certainly never happen on Stack Exchange.