standing on a line by itself, getting converted to this:

Yes, the line above and below are blank. Yes the div tag is starting at the first column It displays as intended. Firefox's browser is clever, but it won't validate, and given all the whinging I've done about non-validating web pages, I better get mine right. I'm processing with template toolkit. If I turn off the multimarkdown filter, this is what's being passed: 32

37 38 39 40 41

42 43 # Contact Info 44 If you want to write, phone, email, drive here this is the place to 45 find out how. 46 32

37 38 39

40 41

Contact Info

42 43

If you want to write, phone, email, drive here this is the place to 44 find out how.

45 As a sanity check I reverted to Markdown instead of multimarkdown No change. Now it wasn't happening in all files An hour of pruning copies of files that worked versus ones that didn't found the following: This file would work: [% USE MARKDOWN %] [% FILTER MARKDOWN %]

[% END #filter markdown %] This file would not work: [% USE MARKDOWN %] [% FILTER MARKDOWN %]

[% END #filter markdown %]

The [% boxes are template toolkit instructions. So TT was NOT handling markdown the closing

in the non-working cases. Markdown couldn't find a closing tag to match the opening tag, therefore it must be text, and gets wrapped in

tags. Go figure. -- Sherwood Botsford Sherwood's Forests Warburg, Alberta T0C 2T0 http://www.sherwoods-forests.com 780-848-2548 From michel.fortin at michelf.com Fri Mar 6 06:17:39 2009 From: michel.fortin at michelf.com (Michel Fortin) Date: Fri, 06 Mar 2009 06:17:39 -0500 Subject: Table of contents In-Reply-To: References: Message-ID: Le 2009-03-05 ? 4:27, Daniel Winterstein a ?crit : > I'm using Markdown in an app and would like to provide support for > including > a table of contents. > Any suggestions for a syntax? Has anyone done this before? > My first thoughts are: > > 1. Have a special header item (using markdown extra's header > syntax), e.g. > > generate-contents: yes Just to make things clear. PHP Markdown Extra doesn't have this kind of metadata syntax. Other implementations do however. > 2. Have a special xml tag with optional alternative text inside, e.g. > > > 1. First thingy > 2. Second thingy > 3. Other stuff > HTML and XML tags shouldn't be part of the Markdown syntax. > 3. Detect that a set of list items matches the first few headers. > E.g. if > the document has headers > > # Monkeys > ## Chimps > ## Humans > ## Proboscis monkeys > ## Other monkeys > ## Do Lemur's count? > > Then a list that ran: > > 1. Monkeys > 1. Chimps > 2. Humans > > Would be detected as the start of a contents list, and the other > entries > would automatically be added to it. This seems the nicest approach > in some > respects, but also the one likely to cause confusion and annoyance. I'd rather have a single tag, or another indicator saying "insert TOC here". Sample TOC content in your element is going fall out of sync with the rest of the document some day when you edit the document; I see no use for it. That said, I believe the best way to generate a TOC is to implement HTML5's outline algorithm, working directly on the HTML or XHTML output. -- Michel Fortin michel.fortin at michelf.com http://michelf.com/ From sgbotsford at gmail.com Fri Mar 6 11:02:49 2009 From: sgbotsford at gmail.com (Sherwood Botsford) Date: Fri, 6 Mar 2009 09:02:49 -0700 Subject: Multi-Markdown meta tag behaviour. Message-ID: <534004cc0903060802v1141074ah5e2d0c2eca04d3ac@mail.gmail.com> I'll admit I'm a bit confused about how MMD handles meta-tags in the document to control it's own behaviour. I tried to turn off id tag generation. [% USE MultiMarkdown %] [% FILTER multimarkdown %] heading_ids: 0 All I get is a line saying heading_ids: 0 in my output. So this is the first line being handed MMD, and a blank line after. Obvious I'm missing something in the syntax. For now I've hacked the default, as I think I prefer it that way. But I can see wehre overriding tags in the doc would be handy. (id tags IMHO should be used sparingly as a means of formatting block level elements) -- Sherwood Botsford Sherwood's Forests Warburg, Alberta T0C 2T0 http://www.sherwoods-forests.com 780-848-2548 From sgbotsford at gmail.com Fri Mar 6 19:44:04 2009 From: sgbotsford at gmail.com (Sherwood Botsford) Date: Fri, 6 Mar 2009 17:44:04 -0700 Subject: Paragraph tags around

blocks In-Reply-To: <534004cc0903051911h46d5c368tf2496e0eb62b1180@mail.gmail.com> References: <534004cc0903051911h46d5c368tf2496e0eb62b1180@mail.gmail.com> Message-ID: <534004cc0903061644y2aa26e1dl81060f69509d2b22@mail.gmail.com> I can now reproduce my problem very simply. [% USE MultiMarkdown %] [% FILTER multimarkdown %] # Headline outside div

# Headline inside div

[% END %] Produces:

Headline outside div

# Headline inside div

-- Sherwood Botsford Sherwood's Forests Warburg, Alberta T0C 2T0 http://www.sherwoods-forests.com 780-848-2548 From sgbotsford at gmail.com Sat Mar 7 01:01:59 2009 From: sgbotsford at gmail.com (Sherwood Botsford) Date: Fri, 6 Mar 2009 23:01:59 -0700 Subject: Paragraph tags around

blocks In-Reply-To: <534004cc0903051911h46d5c368tf2496e0eb62b1180@mail.gmail.com> References: <534004cc0903051911h46d5c368tf2496e0eb62b1180@mail.gmail.com> Message-ID: <534004cc0903062201g7be673ccif8ed7ba353b4ee34@mail.gmail.com> It's a monolog week for me. Answering my own post. Again. Turns out it's not that simple. Consider the following input fragment: (For clarity, I'm compressing the double spacing. All

tags have a blank line before and after. # Headline outside div

# Headline inside div

Run through MMD I get:

Headline outside div

# Headline inside div

IF I use DIV instead of div

Headline outside div

Headline inside div

Which causes the w3c validator the whine. I get this form of result if I have

but the first form of result if I have

This behaviour is identical for both MMD 1.0.24 (CPAN) and for MMD 2.0.b5 (FP's website) I think that the regex that's scaning for a div tag is looking only for a well formed one. Being either wrong case or with a malformed id it's treated as text, and surrounded by

tags. If the divs match the expression it doesn't process the content. -- Sherwood Botsford Sherwood's Forests Warburg, Alberta T0C 2T0 http://www.sherwoods-forests.com 780-848-2548 From mail at milianw.de Sat Mar 7 06:29:42 2009 From: mail at milianw.de (Milian Wolff) Date: Sat, 7 Mar 2009 12:29:42 +0100 Subject: Paragraph tags around

blocks In-Reply-To: <534004cc0903062201g7be673ccif8ed7ba353b4ee34@mail.gmail.com> References: <534004cc0903051911h46d5c368tf2496e0eb62b1180@mail.gmail.com> <534004cc0903062201g7be673ccif8ed7ba353b4ee34@mail.gmail.com> Message-ID: <200903071229.49805.mail@milianw.de> On Saturday 07 March 2009, Sherwood Botsford wrote: > It's a monolog week for me. Answering my own post. Again. > > Turns out it's not that simple. Consider the following input fragment: > (For clarity, I'm compressing the double spacing. All

tags have > a blank line before and after. > > # Headline outside div >

> # Headline inside div >

> > Run through MMD I get: >

Headline outside div

> # Headline inside div >

> > IF I use DIV instead of div >

Headline outside div

> >

Headline inside div

> >

> > Which causes the w3c validator the whine. > I get this form of result if I have

> but the first form of result if I have

> > > This behaviour is identical for both MMD 1.0.24 (CPAN) and for MMD > 2.0.b5 (FP's website) > > I think that the regex that's scaning for a div tag is looking only > for a well formed one. > Being either wrong case or with a malformed id it's treated as text, > and surrounded by

tags. That's a bug. > If the divs match the expression it doesn't process the content. That's how it should be. Markdown does not alter / change stuff inside HTML tags (think or similar). At least PHP Markdown Extra supports a proprietary `markdown="1"` attribute for tags which should get their contents markdowned. -- Milian Wolff mail at milianw.de http://milianw.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. Url : From sgbotsford at gmail.com Sat Mar 7 12:45:26 2009 From: sgbotsford at gmail.com (Sherwood Botsford) Date: Sat, 7 Mar 2009 10:45:26 -0700 Subject: Paragraph tags around

 blocks
In-Reply-To: <534004cc0903062201g7be673ccif8ed7ba353b4ee34@mail.gmail.com>
References: <534004cc0903051911h46d5c368tf2496e0eb62b1180@mail.gmail.com>
	<534004cc0903062201g7be673ccif8ed7ba353b4ee34@mail.gmail.com>
Message-ID: <534004cc0903070945m6c67752p3c831344f38bc4@mail.gmail.com>

The MMD package has a setable item markdown_in_html_blocks.

I hacked the code to make this default on.  At the same time, I turned
off img_ids and heading_ids.

The last two worked.  Told me that I was changing things in the right place.

Didn't seem to matter what value I gave markdown_in_html_blocks. Made
no difference in the behaviour.

Manually taking  out of the list of block level elements however
did allow markdown on stuff inside div blocks
but also resulted in div tags being paragraph formatted.  I suspect
that getting markdown_in_html_blocks working would result in all tags
getting so wrapped.

Looking deeper at the code, the regexen are mind numbingly complex to
one of  my meager skills.
It's not clear to me how to set up a tag that is ignored, but whose
contents are processed.

At this point my workaround will likely be to put some dummy variable
in place such as DIV-pic4 on a line by itself. let it get turned into
DIV-pic4 then do a post process substitution that replaces the
line with the correct div tag.

-- 
Sherwood Botsford
Sherwood's Forests
Warburg, Alberta T0C 2T0
http://www.sherwoods-forests.com
780-848-2548

From waylan at gmail.com  Sun Mar  8 22:27:42 2009
From: waylan at gmail.com (Waylan Limberg)
Date: Sun, 8 Mar 2009 21:27:42 -0500
Subject: Python-Markdown 2.0 Release Candidate
Message-ID: 

I am pleased to announce that after much hard work, a Release
Candidate for Python Markdown version 2.0 is now available for
[download][]. Please, download it, install it, test it, beat it... and
report any [bugs][]. Assuming no major bugs, we will release 2.0 final
approximately one month from today. Until then, the project [site][]
will continue to document version 1.7. Updated documentation is
available in the `doc/` directory in the source files. Hopefully, all
the included extensions will be documented before the final release.

[download]: https://sourceforge.net/project/showfiles.php?group_id=153041&package_id=183331&release_id=666767
[bugs]: http://www.freewisdom.org/projects/python-markdown/Tickets
[site]: http://www.freewisdom.org/projects/python-markdown

Release Notes:
===========

* Major refactor of the core and extension API. Extension authors
should see the included documentation in
`docs/writing_extensions.txt`. All parts of the syntax are now
completely overridable by extensions.

* Numerous extensions added to the standard distribution (off by
default), including an "extra" extension which matches PHP Markdown
Extra. See the `markdown/extensions/` directory for the full list.

* The code has been refactored into a full Python library with a
separate command line script.

* Optional output of XHTML1 (default) or HTML4 with the option for
extensions to add more.

* Uses ElementTree to build (X)HTML document rather than home-grown NanoDom.

* Most of the differences in Python-Markdown's output compared to perl
and/or php have been eliminated.

* And much more... See the changelog and [Git log][] for more details.

[Git log]: http://gitorious.org/projects/python-markdown/repos/mainline/logs

-- 
----
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg

From sgbotsford at gmail.com  Wed Mar 25 11:12:22 2009
From: sgbotsford at gmail.com (Sherwood Botsford)
Date: Wed, 25 Mar 2009 09:12:22 -0600
Subject: surplus  tags.
Message-ID: <534004cc0903250812r47919088yc151e7346038fe78@mail.gmail.com>

I've run into a problem with multimarkdown, and would like advice:  From
Fletcher's doc:
>
>

Unlike PHP Markdown Extra, all definitions are wrapped in 
 tags. First,
> I

was unable to get Markdown not to create paragraphs. Second, I didn?t see

where it mattered - the only difference seems to be aesthetic, and I
> actually

prefer the 
 tags in place. Let me know if this is a problem.

  1. 
 causes W3C's xhtml checker to whine.  All non-ancientbrowsers
do the right thing, so I can ignore it. 2.  The combination of  and the CSS code snippet p {   text-indent: 1em;  } causes the IMAGE
to be indented 1 em.  (presumably since it's in thefirst line of text.) This
also adds an extra em of leading space to my headlings -- that I can live
with.  This is solveable by putting an additional css snippet in
p img {
  margin-left: -1em;
 }
(img doesn't know about text-indent.
This is a hack, and makes for the potential of ugly side effects when
modifying the css code --
something already filled with surprises.
The ideal solution from my perspective is two modifications of MMD that I
can't figure out how to do:
1.  Remove the extra  tagging.
2.  Specify automatically that structural tags get passed through unchanged.
(Structural tags = div, body, html, and those tags that lurk in the head.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: