From pagaltzis at gmx.de  Sat Jun  7 11:42:53 2008
From: pagaltzis at gmx.de (Aristotle Pagaltzis)
Date: Sat, 7 Jun 2008 17:42:53 +0200
Subject: mkhtml.py: writing HTML documents in Markdown
In-Reply-To: <20080520042720.A1182183437@panacea.canonical.org>
References: <20080520042720.A1182183437@panacea.canonical.org>
Message-ID: <20080607154253.GE17586@klangraum.plasmasturm.org>

[Note to markdown-discuss readers: for context see
<http://lists.canonical.org/pipermail/kragen-hacks/2008-June/000488.html>]

* Kragen Javier Sitaker <kragen at pobox.com> [2008-06-07 09:40]:
> Stylesheeting comes naturally. I just put a `<style>` element
> at the top with a few lines inside of it to format nicely.

Note that Markdown ends up wrapping `<link>` and `<style>`
in `<p>` tags, arguably erroneously. Weirdly, it looks like
Python-Markdown should avoid that mistake:

* <http://babelmark.bobtfish.net/?markdown=%3Cstyle%3Efoo+%7B%7D%3C%2Fstyle%3E>
* <http://babelmark.bobtfish.net/?markdown=%3Clink+%2F%3E>

But at the top of <http://canonical.org/~kragen/crywrap.html> the
problem shows up anyway.

Of course, neither tag has any business being in the HTML body;
they should both be in the head. Since you?re loading
BeautifulSoup anyway, you probably want to include that as fix-up
step in your postprocessing.

Regards,
-- 
Aristotle Pagaltzis // <http://plasmasturm.org/>

From waylan at gmail.com  Sat Jun  7 22:34:30 2008
From: waylan at gmail.com (Waylan Limberg)
Date: Sat, 7 Jun 2008 22:34:30 -0400
Subject: mkhtml.py: writing HTML documents in Markdown
In-Reply-To: <20080607154253.GE17586@klangraum.plasmasturm.org>
References: <20080520042720.A1182183437@panacea.canonical.org>
	<20080607154253.GE17586@klangraum.plasmasturm.org>
Message-ID: <e5d795bb0806071934u7c6db9abs3821b363f5fefa42@mail.gmail.com>

On Sat, Jun 7, 2008 at 11:42 AM, Aristotle Pagaltzis <pagaltzis at gmx.de> wrote:
> [Note to markdown-discuss readers: for context see
> <http://lists.canonical.org/pipermail/kragen-hacks/2008-June/000488.html>]
>
> * Kragen Javier Sitaker <kragen at pobox.com> [2008-06-07 09:40]:
>> Stylesheeting comes naturally. I just put a `<style>` element
>> at the top with a few lines inside of it to format nicely.
>
> Note that Markdown ends up wrapping `<link>` and `<style>`
> in `<p>` tags, arguably erroneously. Weirdly, it looks like
> Python-Markdown should avoid that mistake:

Well, first of all, he's using an old version of Python-Markdown. The
first line of his `render` function gives it away (due to the change
in 1.7 to all-unicode -- you generally don't pass unicode text to
str())

        body = str(markdown.Markdown(text))

Just use the wrapper (all lowercase in any version):

        body = markdown.markdown(text)

IIRC, there was a bugfix in 1.7 that also addressed the raw html
wrapped in <p> tags thing. So, upgrade to 1.7 and that problem should
go away.



-- 
----
Waylan Limberg
waylan at gmail.com

From pagaltzis at gmx.de  Sun Jun  8 14:19:39 2008
From: pagaltzis at gmx.de (Aristotle Pagaltzis)
Date: Sun, 8 Jun 2008 20:19:39 +0200
Subject: mkhtml.py: writing HTML documents in Markdown
In-Reply-To: <20080608155903.D79041834A3@panacea.canonical.org>
References: <20080520042720.A1182183437@panacea.canonical.org>
	<20080607154253.GE17586@klangraum.plasmasturm.org>
	<20080608155903.D79041834A3@panacea.canonical.org>
Message-ID: <20080608181939.GJ17586@klangraum.plasmasturm.org>

* Kragen Javier Sitaker <kragen at canonical.org> [2008-06-08 18:00]:
> On Sat, 7 Jun 2008 17:42:53 +0200, Aristotle Pagaltzis wrote:
> > * Kragen Javier Sitaker <kragen at pobox.com> [2008-06-07 09:40]:
> > > Stylesheeting comes naturally. I just put a `<style>`
> > > element at the top with a few lines inside of it to format
> > > nicely.
> > 
> > Note that Markdown ends up wrapping `<link>` and `<style>` in
> > `<p>` tags, arguably erroneously.
> 
> What, is Markdown supposed to know that those elements are
> neither block-level nor span-level markup?

In fact it is ? or to phrase the statement more appropriately, it
is supposed to know that wrapping such elements in `<p>` tags is
not a useful thing to do. It already avoids wrapping block-level
tags in paragraphs; there is no reason not to extend that list to
also contain all the elements that may appear in the head of an
HTML document, even though they are nominally invalid in the body.

> > Of course, neither tag has any business being in the HTML
> > body; they should both be in the head. Since you?re loading
> > BeautifulSoup anyway, you probably want to include that as
> > fix-up step in your postprocessing.
> 
> Yeah, I've been planning to do that, but didn't get around to
> doing it before sending it out.  (I also have this theory that
> I'll be a happier person if I don't spend too much time on
> inventing private markup languages, and that makes me perhaps
> unreasonably reluctant to add extra postprocessing steps, even
> when the alternative is ill-formed HTML.)

I agree with that theory, which is why I use Markdown despite the
minor (and a few less minor) things I dislike about it. Attaching
some light postprocessing to Markdown to add support for small
missing bits seems like a much better approach to achieve both
satisfaction and an absence of unhappiness.

I try to write code only when I can?t help it?

Regards,
-- 
Aristotle Pagaltzis // <http://plasmasturm.org/>

From michel.fortin at michelf.com  Sat Jun 21 22:27:28 2008
From: michel.fortin at michelf.com (Michel Fortin)
Date: Sat, 21 Jun 2008 22:27:28 -0400
Subject: [ANN] PHP Markdown 1.0.1m & Extra 1.2.2
Message-ID: <34C3DC4F-10EB-4D50-AB77-251260C4CAA5@michelf.com>

Here's another update to PHP Markdown and PHP Markdown Extra featuring  
some bug fixes.

See the download link on the project's page:
<http://michelf.com/projects/php-markdown/>

This update also features a new emphasis parser which process regular  
and strong emphasis in one pass instead of two and four for previous  
versions of PHP Markdown and PHP Markdown Extra. The new parser is  
also faster and easier to change if the logic needs to be adjusted. It  
works by using context-dependent composition of a regular expression  
for matching allowed emphasis tokens, and PHP code to generate proper  
emphasis elements from the tokens.


1.0.1m:

*	Lists can now have empty items.

*	Rewrote the emphasis and strong emphasis parser to fix some issues
	with odly placed and overlong markers.


Extra 1.2.2:

*	Fixed a problem where abbreviation definitions, footnote
	definitions and link references were stripped inside
	fenced code blocks.

*	Fixed a bug where characters such as `"` in abbreviation
	definitions weren't properly encoded to HTML entities.

*	Fixed a bug where double quotes `"` were not correctly encoded
	as HTML entities when used inside a footnote reference id.


Michel Fortin
michel.fortin at michelf.com
http://michelf.com/