From daniel.winterstein at gmail.com Fri May 1 07:41:46 2009 From: daniel.winterstein at gmail.com (Daniel Winterstein) Date: Fri, 1 May 2009 12:41:46 +0100 Subject: Including external files Message-ID: I quite often find myself making documents that pull together other fragmentary documents. Does anyone have suggestions for an include or embed syntax? I.e. a way of saying "pull in the contents of document X here". Has this been implemented before? Such a syntax might be: (embed: snippet.txt) or [include](snippet.txt) Your thoughts? Best regards, - Daniel From sgbotsford at gmail.com Fri May 1 08:04:53 2009 From: sgbotsford at gmail.com (Sherwood Botsford) Date: Fri, 1 May 2009 06:04:53 -0600 Subject: Including external files In-Reply-To: References: Message-ID: <534004cc0905010504n7c8b5371uff5fe5d6e6cb549c@mail.gmail.com> Template toolkit. Here's a sample: [% PROCESS header.inc Title = "Sherwood's Forests -- Almanac" Desc = "Sherwood's Forests life at the tree farm." %]

[% FILTER multimarkdown %] # Sherwood's Almanac #### Week starting 22 March 2009 *** [% PROCESS Copyright.inc %][% END %]

[% INCLUDE footer.inc %] That's the blank template I use for my blog. PROCESS allows you to pass data to the include file. INCLUDE just includes it verbatim with no processing by the template system. Therer is also INSERT which works like process, but acts like it's call-by-value instead of call-by-reference for the name space. In my case, header.inc builds the menu, Copyright.inc has the copyright info and also a link back to the top of the page. (My Bad: my pages tend to be 3-4 screens long.) Footer has the document end and a couple of google Adsense boxes. -- Sherwood Botsford Sherwood's Forests Warburg, Alberta T0C 2T0 http://www.sherwoods-forests.com 780-848-2548 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jklewis at umich.edu Fri May 1 14:27:15 2009 From: jklewis at umich.edu (John Kipling Lewis) Date: Fri, 1 May 2009 14:27:15 -0400 (EDT) Subject: Hello. I'm new so forgive my ignorance of previous ideas. Message-ID: <20090501142010.N67627@maniac.deathstar.org> One thing I thought might be useful for Markdown was logic that converted certain text to tags. Since Markdown is often used as a way to transfer information from email and there is a convention for simulating deleted text in email it might make a nice addition. Example: I really love^H^H^H^H hate you. becomes, I really ~~love~~ hate you. [Reference](http://en.wikipedia.org/wiki/Backspace) Thoughts? Too specific? Too geeky? On target? Nice Easter Egg? John - From waylan at gmail.com Fri May 1 14:54:15 2009 From: waylan at gmail.com (Waylan Limberg) Date: Fri, 1 May 2009 14:54:15 -0400 Subject: Hello. I'm new so forgive my ignorance of previous ideas. In-Reply-To: <20090501142010.N67627@maniac.deathstar.org> References: <20090501142010.N67627@maniac.deathstar.org> Message-ID: On Fri, May 1, 2009 at 2:27 PM, John Kipling Lewis wrote: > > One thing I thought might be useful for Markdown was logic that converted > certain text to tags. ?Since Markdown is often used as a way to > transfer information from email and there is a convention for simulating > deleted text in email it might make a nice addition. > > Example: > > I really love^H^H^H^H hate you. > > becomes, > > I really ~~love~~ hate you. Well, I'd say this is both easier to read and write than your example above. As readability is a top priority and markdown allows raw html, I don't see any need for a way to markup deleted text accept with raw html - which we already have. -- ---- \X/ /-\ `/ |_ /-\ |\| Waylan Limberg From jklewis at umich.edu Mon May 4 10:23:09 2009 From: jklewis at umich.edu (John Kipling Lewis) Date: Mon, 4 May 2009 10:23:09 -0400 (EDT) Subject: No subject In-Reply-To: References: Message-ID: <20090504101943.J24560@maniac.deathstar.org> I suppose I didn't mean to *replace* the existing system in favour of this one, but rather augment markdown from one of it's stated goals: "...the single biggest source of inspiration for Markdown.s syntax is the format of plain text email." It's common practice to add^H^H^H put these makes in for clarity. In current Markdown they would be represented as normal text, but the intention of the writer is strikethrough. Perhaps there's no room in markdown for this enhancement in the name of a minor feature. This is understandable. From qaramazov at gmail.com Mon May 4 14:28:51 2009 From: qaramazov at gmail.com (Yuri Takhteyev) Date: Mon, 4 May 2009 11:28:51 -0700 Subject: In-Reply-To: <20090504101943.J24560@maniac.deathstar.org> References: <20090504101943.J24560@maniac.deathstar.org> Message-ID: > Perhaps there's no room in markdown for this enhancement in the name of a > minor feature. This is understandable. It is entirely reasonable, I think, that some people want specific "minor" features that do not have broad enough support to make them standard (and thus a requirement for all implementations). This is the main reason why with python markdown we have focused on making it easy to add such features as extensions. The feature you are proposing is exactly the kind of things we've had in mind. - yuri -- http://spu.tnik.org/ From orc at pell.chi.il.us Mon May 4 15:41:40 2009 From: orc at pell.chi.il.us (david parsons) Date: 4 May 2009 19:41:40 GMT Subject: Mail article References: <20090504101943.J24560@maniac.deathstar.org> Message-ID: In article <20090504101943.J24560 at maniac.deathstar.org>, John Kipling Lewis wrote: >It's common practice to add^H^H^H put these makes in for clarity. Common practice where? I used to see that construction on usenet, and occasionally I use it in mail, but in my experience the whole point of typing out ^H & ^W is so that your reader will see it and be amused by what you're writing. (I occasionally use strikethrough when writing on weblogs, but I don't think it looks as good as the visual attempt to frantically backspace over some intemperate but true invective.) And from a usability point of view, I don't think it's all that great because you'd need to keep track of how many characters you're backspacing over. -david parsons From jklewis at umich.edu Tue May 5 12:10:55 2009 From: jklewis at umich.edu (John Kipling Lewis) Date: Tue, 5 May 2009 12:10:55 -0400 (EDT) Subject: Markdown-Discuss Digest, Vol 72, Issue 4 In-Reply-To: References: Message-ID: <20090505120944.H73745@maniac.deathstar.org> It makes sense to have this as an add-on module (as the Python system apparently has.) As for the "common usage", I suppose I'm just old. From joehall at gmail.com Thu May 7 17:06:59 2009 From: joehall at gmail.com (Joseph Lorenzo Hall) Date: Thu, 7 May 2009 17:06:59 -0400 Subject: homemade fn marker weirdness... Message-ID: <928946aa0905071406v51e2c8d5h307ad1eec6ab524c@mail.gmail.com> so this is a weird one: http://babelmark.bobtfish.net/?markdown=%3Csup%3E*%3C%2Fsup%3EThe+[distinction]+between+certification+and+qualification%2C+although+vague%2C+appears+to+be+that+under+the+NASED+system%2C+states+did+the+ultimate+*certification*+of+a+voting+system+for+fitness+in+future+elections. Note that the `^*` is being turned into `` Here's a smaller more general case: http://babelmark.bobtfish.net/?markdown=%3Csup%3E*%3C%2Fsup%3Eblah+*blah*+blah&src=1&dest=2 Although note that if I remove emphasis from the fn, it's fine: http://babelmark.bobtfish.net/?markdown=%3Csup%3E*%3C%2Fsup%3Eblah+blah+blah&src=1&dest=2 best, Joe -- Joseph Lorenzo Hall ACCURATE Postdoctoral Research Associate UC Berkeley School of Information Princeton Center for Information Technology Policy http://josephhall.org/ From qaramazov at gmail.com Thu May 7 17:40:32 2009 From: qaramazov at gmail.com (Yuri Takhteyev) Date: Thu, 7 May 2009 14:40:32 -0700 Subject: homemade fn marker weirdness... In-Reply-To: <928946aa0905071406v51e2c8d5h307ad1eec6ab524c@mail.gmail.com> References: <928946aa0905071406v51e2c8d5h307ad1eec6ab524c@mail.gmail.com> Message-ID: > Note that the `^*` is being turned into `` Use python markdown 1.7, which doesn't do this. :) However, this is arguably the "correct" behavior and we've in fact _fixed_ this in the newer version of the python implementation, so that it now behaves like all other implementations. HTML tags are essentially getting ignored (as they should), so what you really have is: blah * blah blah blah blah blah *certification* of blah blah. so, the first * becomes and the third one becomes . Why it's the third and not the second, though I don't know. The new python markdown converts the second * into the closing em. - yuri -- http://spu.tnik.org/ From waylan at gmail.com Thu May 7 17:50:29 2009 From: waylan at gmail.com (Waylan Limberg) Date: Thu, 7 May 2009 17:50:29 -0400 Subject: homemade fn marker weirdness... In-Reply-To: References: <928946aa0905071406v51e2c8d5h307ad1eec6ab524c@mail.gmail.com> Message-ID: On Thu, May 7, 2009 at 5:40 PM, Yuri Takhteyev wrote: >> Note that the `^*` is being turned into `` > > > HTML tags are essentially getting ignored (as they should), so what > you really have is: > > ? ?blah * blah blah blah blah blah ?*certification* of blah blah. > Thus, if you do not want one of those *'s to be part of an em, you need to escape it. ^\*blah *blah* blah http://babelmark.bobtfish.net/?markdown=^{\*<%2Fsup>blah+*blah*+blah

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

From joehall at gmail.com Thu May 7 18:51:28 2009
From: joehall at gmail.com (Joseph Lorenzo Hall)
Date: Thu, 7 May 2009 18:51:28 -0400
Subject: homemade fn marker weirdness...
In-Reply-To:
References: <928946aa0905071406v51e2c8d5h307ad1eec6ab524c@mail.gmail.com>

Message-ID: <928946aa0905071551i27b76cfdqde447d548fb65ce6@mail.gmail.com>

Thanks, guys. Apologies for not knowing this was a known issue. best, Joe

From sgbotsford at gmail.com Thu May 7 19:12:21 2009
From: sgbotsford at gmail.com (Sherwood Botsford)
Date: Thu, 7 May 2009 17:12:21 -0600
Subject: homemade fn marker weirdness...
In-Reply-To:
References: <928946aa0905071406v51e2c8d5h307ad1eec6ab524c@mail.gmail.com>

Message-ID: <534004cc0905071612l39f5b80dscf5897b141d2b241@mail.gmail.com>

Ok, Now I'm confused. I have to jump through hoops to get markdown to WORK
between and
And here it's working between ^{and when it's not wanted.

* is overloaded.

1. * is a list indicator.
2. * is an emphasis indicator.
3. * when followed by * * is a ruler indicator.

Normally I would think that a * at the end of block of text without an
opening * to be a footnote indicator..

Thus
*this* becomes this
But
this and that* is printed verbatim.

Now sup and sub are normally short range tags -- you expect the close to be
nearby. So I would also expect that if you've inserted them, you should be
willing to
take over from markdown for the duration. So I'd expect

*this and that^{* __and__ the other* to become this and
that* andthe other

(And I still wish that _ and * were orthoganol and independent. How do I
strongly emphasise something.)

I'm beginning to think that markdown has it backward in some respects:

My limited understanding is that it is nominally inactive inside structural
(div, html, body) and block (table, code, pre, quote ...) and
active in inline tags (span, tr, td, sup, sub, em, strong ...)

I'll admit I've never used sup and sub

Most of the time MD does exactly what I want. sometimes I can't do it in MD
(float a picture and it's caption right) and I have to put html in. My
current system the only time I need to do that is for DIV. But I could see
merit in having either a commandline option or an .rc file option to tell MD
what tags to work inside, and what not.

(for superscript I can see merit in using ^ notation but I can't think of a
good equivalent for sub. And ideally ^ could be closed by either another ^
or by a space.

Thus: (x + y)^3 = x^3 + 2x^2^y + 2xy^2 + y^3

Ok. Lambast me with 27 counter examples of how wrong I am. I can take it.
I won't cry. (much.)

On Thu, May 7, 2009 at 3:50 PM, Waylan Limberg wrote:

> On Thu, May 7, 2009 at 5:40 PM, Yuri Takhteyev
> wrote:
> >> Note that the `^*` is being turned into ``
> >
> >
> > HTML tags are essentially getting ignored (as they should), so what
> > you really have is:
> >
> > blah * blah blah blah blah blah *certification* of blah blah.
> >
>
> Thus, if you do not want one of those *'s to be part of an em, you
> need to escape it.
>
> ^\*blah *blah* blah
>
> http://babelmark.bobtfish.net/?markdown=^{\*<%2Fsup>blah+*blah*+blah
>
> --
> ----
> \X/ /-\ `/ |_ /-\ |\|
> Waylan Limberg
> _______________________________________________
> Markdown-Discuss mailing list
> Markdown-Discuss at six.pairlist.net
> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>

--
Sherwood Botsford
Sherwood's Forests
Warburg, Alberta T0C 2T0
http://www.sherwoods-forests.com
780-848-2548
-------------- next part --------------
An HTML attachment was scrubbed...
URL:

From jgm at berkeley.edu Thu May 7 22:26:30 2009
From: jgm at berkeley.edu (John MacFarlane)
Date: Thu, 7 May 2009 19:26:30 -0700
Subject: homemade fn marker weirdness...
In-Reply-To:
References: <928946aa0905071406v51e2c8d5h307ad1eec6ab524c@mail.gmail.com>

Message-ID: <20090508022630.GA11421@protagoras.phil.berkeley.edu>

+++ Waylan Limberg [May 07 09 17:50 ]:
> On Thu, May 7, 2009 at 5:40 PM, Yuri Takhteyev wrote:
> >> Note that the `^*` is being turned into ``
> >
> >
> > HTML tags are essentially getting ignored (as they should), so what
> > you really have is:
> >
> > ? ?blah * blah blah blah blah blah ?*certification* of blah blah.
> >
>
> Thus, if you do not want one of those *'s to be part of an em, you
> need to escape it.
>
> ^\*blah *blah* blah

Or use peg-markdown, which has better heuristics. :)

From tleggett at optusnet.com.au Mon May 18 21:00:34 2009
From: tleggett at optusnet.com.au (Tony Leggett)
Date: Tue, 19 May 2009 11:00:34 +1000
Subject: Links opening in a new window?
Message-ID:

Hi all,

This is a Noob question but I couldn't find anything on the syntax
page about making a link that opens in a hew window (and two years of
email archives was too much).

For eg. with "This is an [example link](http://example.com/)" where do
I put target="_blank" or its equivalent so it opens in a new page?

Any help would be greatly appreciated.

Thx

Tony

From minhee at dahlia.kr Mon May 18 21:16:44 2009
From: minhee at dahlia.kr (Hong MinHee)
Date: Tue, 19 May 2009 10:16:44 +0900
Subject: Links opening in a new window?
In-Reply-To:
References:
Message-ID:

Explicit frame target of anchors is invalid in XHTML 1.0 Strict.
(There are many issues on web accessibility about it.) Markdown
specifications don?t mention about it, but you can make it with just
raw HTML directly.

On Tue, May 19, 2009 at 10:00 AM, Tony Leggett wrote:
> Hi all,
>
> This is a Noob question but I couldn't find anything on the syntax page
> about making a link that opens in a hew window (and two years of email
> archives was too much).
>
> For eg. with "This is an [example link](http://example.com/)" where do I put
> target="_blank" or its equivalent so it opens in a new page?
>
> Any help would be greatly appreciated.
>
> Thx
>
> Tony
>
>
> _______________________________________________
> Markdown-Discuss mailing list
> Markdown-Discuss at six.pairlist.net
> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>

--
??? Hong, MinHee
http://dahlia.kr/

From tom at jumpingrock.net Mon May 18 22:22:17 2009
From: tom at jumpingrock.net (Tom Humiston)
Date: Mon, 18 May 2009 22:22:17 -0400
Subject: Links opening in a new window?
In-Reply-To:
References:

Message-ID:

Here's an excellent article on the topic:

http://www.useit.com/alertbox/990530.html

In the first two sections of the article, Jakob Nielsen covers issues
related to opening new windows. His website is a gold mine of
information for website designers.

On May 18, 2009, at 9:16 PM, Hong MinHee wrote:

> Explicit frame target of anchors is invalid in XHTML 1.0 Strict.
> (There are many issues on web accessibility about it.) Markdown
> specifications don?t mention about it, but you can make it with
> just raw HTML directly.
>
> On Tue, May 19, 2009 at 10:00 AM, Tony Leggett
> wrote:
>
>> Hi all,
>>
>> This is a Noob question but I couldn't find anything on the syntax
>> page about making a link that opens in a hew window (and two years
>> of email archives was too much).
>>
>> For eg. with "This is an [example link](http://example.com/)"
>> where do I put target="_blank" or its equivalent so it opens in a
>> new page?
>>
>> Any help would be greatly appreciated.
>>
>> Thx
>>
>> Tony}}}}