-
-
Notifications
You must be signed in to change notification settings - Fork 11.2k
Compatibility
Other places where Markdown Here works, besides Thunderbird, Gmail, Hotmail, and Yahoo.
If you find a new problem (or improvement!), or if you find a site that (almost) works, or if you have workflow suggestions, please edit this wiki page, or create a Github issue, or post to the MDH Google Group.
Markdown Here works with Google Groups posts. You can use it in the GG rich compose box, or when you're posting via email. One caveat: Digest emails strip all styling.
A user discovered that Markdown Here works in the Evernote web interface.
As of version 2.9.0, earlier problems are fixed and Blogger is working well. Part of the fix came from changes to the default styling. If you've never customized your CSS, you should click the "Reset to Default" button for the "Primary Styling CSS". If you have customized your CSS, you can take a look at the default CSS and decide what to take.
Minor caveat: Some syntax highlighting themes with dark backgrounds don't seem to show up properly. There's an example at the bottom of this post.
Thanks to lambdaalice for originally reporting that MDH worked with Blogger and for detailing the previous bad behaviour.
Google Sites seems to use an editor similar to Gmail and Google Groups. I haven't tested a lot, but Markdown Here seems to work very well with it.
You can see some test pages here.
As of version 2.9.0, earlier problems are fixed and Wordpress is working well. Part of the fix came from changes to the default styling. If you've never customized your CSS, you should click the "Reset to Default" button for the "Primary Styling CSS". If you have customized your CSS, you can take a look at the default CSS and decide what to take.
Caveats and tips:
- The Wordpress "Preview" button is your friend. What you see there (but not so much in the edit box) is what you get.
- After rendering, inline code appears in a non-monospace font, but it is correctly monospace in the preview and in the finished post.
- The section below on Pasting vs. Typing applies here.
- Like with the Yahoo rich controls, if the paragraph type combo is clicked, focused-element finding gets busted and Markdown Toggle stops working. See issue #16.
Thanks to Sina Iravanian for originally discovering that MDH works with Wordpress.
Check out a test post.
Postbox is a non-free desktop email client based on Thunderbird, and user markgoodson requested that Markdown Here support it. The Mozilla extension now works with it, but with some major caveats:
- There's no options page. However, you can open the "Config Editor" from the Preferences dialog and copy/paste options from Firefox's or Thunderbird's equivalent config editor (
about:configin Firefox, "Config Editor" in Thunderbird). Note: Make them all string values.- I just couldn't figure out how to open a tab with the options page. This will probably require the assistance of Postbox or someone familiar with developing for it.
- Line breaks can appear mysteriously in code blocks. Postbox seems to insert unescaped newlines into the raw email when sending, which cause problems if they appear in the middle of a
<pre>block. - Gmail and Thunderbird reply exclusion doesn't work in Postbox. It doesn't seem to put the original email in a
<blockquote>. You will have to use Markdown Here's selection conversion, like with Yahoo and Hotmail. - Postbox won't be a first-class client for Markdown Here, partly because my trial license for it expires soon. If something breaks, create an issue.
Facebook "Notes" feature users TinyMCE as its editor, so MDH kinda works. But there are caveats.
- The Preview function doesn't play well with Markdown Here. If write some stuff, then MDH-render, then preview, and decide to go back to edit some more... you can't un-render back to Markdown. (It has stripped out the special MDH stuff.)
- Pasting plaintext seems to lose newlines completely. This is weird and annoying, but actually helps prevent TinyMCE's Pasting vs. Typing confusion.
- Only the formatting types presented on the Notes' formatting toolbar are supported, at all. If you put a Markdown code block into the edit box and MDH-render it, it will look fine in the editor, but if you preview or publish it, you'll see that it's been stripped out.
- Italics doesn't work in preview/publish. The italicize button on the Notes' formatting toolbar behaves that same broken way as well.
Ctrl+Iworks, though. It seems that Notes doesn't allow<em>but does allow<i>.
The Google Hangouts web interface supports limited rich editing -- bold, italics, and underline. Markdown Here can format bold and italics in the interface, with caveats:
- The surrounding
<p>element makes the little compose box look oddly expanded after rendering. There's no ill effect, though. - In Chrome, the chat box has to be popped out of the Gmail page in order for MDH to work. This is because (I think) MDH is loaded into the Gmail page and there are cross-origin restrictions between the top
mail.google.compage and thetalkgadget.google.comiframewhere the chat box is.- Firefox doesn't have this problem. Opera surely does. Not sure about Safari.
There's a whole class of rich editors for use in web pages that Markdown Here woks with.
TinyMCE is an open source "web based Javascript HTML WYSIWYG editor control". It's used as a rich edit control by these sites (at this time), among others: Evernote, Wordpress, Facebook (Notes). It seems to have lots of customization options for changing the way it works and what formatting it allows and doesn't. Individual sites of reasonable importance with idiosyncratic behaviour should still have a separate section on this page.
TinyMCE inserts <p> elements on every Enter keypress. Prior to Markdown Here version 2.9.0, this would cause extra blank lines in code blocks, break tables, and probably other bad things. MDH's <p>-vs-<br> detection basically fixes this. (Although it will looks odd when writing, since there's more space between newlines than one expects when writing Markdown.)
An annoying TinyMCE oddity is that pasting plain-text is not the same as typing. When pasting multi-line text, line breaks (<br>) are inserted; when typing, paragraphs (<p>) are created.
This can cause Markdown Here to be confused about what rendering method to use. So, generally speaking, it's best to not mix and match multi-line pasted and typed Markdown. And if you do paste some stuff, try to render it separately using a selection.
CKEditor seems to be exactly the same (for our purposes) as TinyMCE -- both in what it is and how it behaves. So read that section.
Aloha Editor is also an open source rich web editor. Like TinyMCE it inserts <p> elements, but unlike TinyMCE it doesn't switch to <br> when pasting. Markdown Here seems to render it quite well.
Redactor is a rich editor, like TinyMCE (but not open source). Like TinyMCE it inserts <p> elements, but unlike TinyMCE it doesn't switch to <br> when pasting. Markdown Here seems to work pretty well with it, with caveats:
- Code blocks have a background colour and an outer border. This can probably be defeated with site-specific rules and
!important. See the default Primary Styling CSS for an example used with Wordpress. - Some other styling stuff.
Hallo is a simple rich editor. Markdown Here seems to work reasonably well with it.
wysihtml5 is also an open-source rich editor. It inserts <br> on each Enter. Markdown Here seems to work pretty well with it.
bootstrap-wysihtml5 is based on wysihtml5 for use with the Twitter Bootstrap web toolkit. Markdown Here works well with it as well.