similar to: UTF-8 BOM

Time for an update to PHP Markdown and PHP Markdown Extra. <http://michelf.com/project/php-markdown/> This new version of PHP Markdown Extra adds support for "fenced" code blocks (which I was previously calling "flat"). Fenced code blocks overcome many limitations of Markdown's indented code blocks: they can can be put immediately following a list item, can

Is there any way for flac or metaflac to support input from files with Unicode Byte Order Marks (BOM)? In command: metaflac --remove-all-tags --set-tag-from-file="CUESHEET=CDImage.cue" --set-tag-from-file="LOGFILE=CDImage.log" CDImage.flac If "CDImage.cue" contains Unicode characters, most text editors append BOM at the 1st line of this file. And metaflac does not

Hi, I'm in the process of adding support for Markdown to a minimal CMS in Rails, [Railfrog][railfrog], which uses mime types to select appropriate processing. I have had a look through the archives but have not been able to see that a consensus has emerged as to what such a mime type for Markdown should look like. My reading of the RFCs suggests that it should be within the "text/*"

Hello all, I've began writing the parsing section of the spec, and I though I'd let you know about where I'm heading with all this. Basically, parsing is defined as three consecutive passes: parsing document elements, parsing block elements and parsing span elements. Each pass is going to contain a set of rules the parser should attempt to match while parsing the input. Rules

I'm currently attempting to write a spec for parsing Markdown Extra, and since one goal is to minimize the differences in output between implementations, I've made a tool allowing me to compare who does what for any given input. I hope this can also facilitate future discussions about the syntax. So here's Babelmark, a testbed for various Markdown implementations were you

Markdowners, just a short heads-up to a newly released Markdown implementation: "pegdown" (http://github.com/sirthias/pegdown) implements a Java Markdown-to-HTML processor based on a PEG parser with the grammar being based on John MacFarlanes C implementation "peg-markdown". pegdown uses "parboiled" (http://www.parboiled.org) for the actual parsing work and, as

This update to PHP Markdown fix a bug that slipped in the WordPress interface with the last update. It also introduce a new "feature": you can now instruct the parser to ignore HTML tags and/or entities in the input. You can do this by instantiating yourself the parser and setting the `no_markup` or `no_entities` properties to true: $parser = new Markdown_Parser;

>>> I'm not sure the indentation feature is so useful. After all, you >>> can use the old syntax if you want indentation. What do you think? >> >> I'd prefer to keep it simple and leave out the indentation feature. I would also prefer to leave this out. >>> Perhaps an alternative would be to use ++++s instead of ~~~~s. >> Advantages: Not

Hello, What should the following input produce? Dutch has shifted Germanic g to the velar fricatives [?] and [x], but retained the spelling with <g> and thus at least a visual similarity to German; English and Frisian have shifted g to [j] before palatal vowels The Dingus says: <p>Dutch has shifted Germanic g to the velar fricatives [?] and [x], but retained the spelling

Does anyone know which version of Markdown is best for Wordpress? I see online that there are a few and was wondering which one people prefer. Also, is there any chance John Gruber will write an official Markdown plugin for Wordpress, given how popular it's becoming? -------------------------------------------------------- robdumas at gmail.com http://obnoxio.us/

I'm using Michel Fortin's MDTest cases to rewrite my html2text.php script. Just now I stumbled upon this bug (in PHP Markdown at least): # Input: Backtick: ``\``` # Output: <p>Backtick: ``&#96;``</p> # Should-Be Output: <p>Backtick: <code>`</code></p> If you (Michel) are already aware of this, just ignore me ;-) -- Milian Wolff

The following benchmarks have been obtained using the TextMate manual as the input source: <http://macromates.com/textmate/manual/source.tbz> Using PHP Markdown, parsing the 24 files separately (with the reference file appended to each of them), I get this (on an iBook G4 1.2 Ghz): Total Avg. Min. Q1. Med. Q3. Max. Parse Time (ms):

So here's an interesting bug I just discovered: [Like this][d]: [here][h]. [d]: foo [h]: bar The output here should be: <a href="foo">Like this</a>: <a href="bar">here</a>. But instead the output is completely empty. I see this bug in both Markdown.pl and PHP Markdown. The problem is that all three lines are being

This is a new release for PHP Markdown, following Markdown.pl 1.0.2b7 from a few weeks ago. It fix the same bugs, and some more; it also introduce more radical backend changes. It can be downloaded here: <http://www.michelf.com/docs/projets/php-markdown-1.0.2b7.zip> and you can test it on the PHP Markdown Dingus: <http://www.michelf.com/projects/php-markdown/dingus/> This

I just received a report [1] that the footnote output we use in Python-Markdown (an exact copy of PHP Markdown Extra [3]) is not valid HTML [3]. If you notice he's using HTML5. At least the footnote syntax does valid on XHTML1 or HTML4. Anyway, any suggestions on how the various footnote implementations want to move forward with this? [1]: https://github.com/waylan/Python-Markdown/issues/129

Python-markdown currently replaces all straight quotes (`"`) with the html entity (`&quot;`). Someone recently complained about this in a [bug report][]. As it turns out the quote was the symptom that brought the real problem to light[^1]. In any event, the reporter pointed out that markdown.pl does not replace straight quotes with the html entity. I know John Gruber has mentioned before

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm redesigning my site and considering moving from Movable Type to WP, but many of my entries are in Markdown. I really, really like Markdown and SmartyPants. I've not used Textile much, but Markdown feels more natural to me; also, I love SmartyPants because I'm a stickler for curly quotes. I understand there's a Markdown

This is not a question but a report on the difficulties I had and the solution I found with respect to UTF-8, YAML::load, and Ruby/Rails. Comments are appreciated. - - - I had been struggling for two days to get UTF-8 working in my Rails app. I had/have a localization file, lib\locale\de.yml, that had iso-8859-1 encoding. I could not get that to display properly. Marnen, quite correctly,

I just recently became aware of MarkdownTest_1.0.3 (which discount fails, due to the behavior of code blocks changing from "leave whitespace alone except on the first line" to "leave whitespace alone", and the addition of a new kind of magic link that doesn't seem to be documented); is this the most recent version of the test suite, or is there a newer one out there?

Gentlefolk, ______________________________________________________ the setup CMS: WordPress 1.5.2 Markdown version: 1.0.1c Markdown implementation: PHP version by Michel Fortin other active WP plugins: none URL: <http://betweenborders.com/reflections/field-notes-from-inside-a-car/> ______________________________________________________ the pre-processed