Picon

crowd-sourcing for a new javascript browser-based prose editor

marijn haverbeke said:
>   Sometimes I lie awake at night, 
>   feverishly searching for new ways to 
>   load myself down with more 
>   poorly-paying responsibilities. 
>   And then it comes to me: I should 
>   start another open-source project!
>
>   http://marijnhaverbeke.nl/blog/prosemirror.html

crowd-sourcing for a browser-based rich-text editor
based on markdown and/or commonmark, whatever.

one of marjin's earlier projects created _codemirror_,
which is targeted at code. and he now attacks prose.
he also wrote "eloquent javascript", so he might be
one of the best people to write this javascript code.

more:
>   http://marijnhaverbeke.nl/blog/collaborative-editing.html
>   http://prosemirror.net

-bowerbird
Gerald Bauer | 4 Aug 11:16 2015
Picon

HTML Tags <=> Markdown Quick Reference <at> Write Kit

Hello,

  I've started a quick reference that lists all HTML tag with Markdown
"short codes" [1]. The tags include:

HTML                            | Notes
------------------------------- | ---------------------
<h1>...</h1> - <h6>...</h6>     | Heading 1-6
<p>...</p>                      | Paragraph
<br>                            | Hard Line Break
<i>...</i>                      | Italic Text (Emphasis)
<b>...</b>                      | Bold Text (Strong Emphasis)
<code>...</code>                | Code (Monospace Text)
<del>...</del>                  | Deleted (Strikethrough) Text
<ul>(<li>...</li>)+</ul>        | Unordered List
<ol>(<li>...</li>)+</ol>        | Ordered (Numbered) List
<a href="...">...</a>           | Link
<img src="..." alt="...">                   | Image (with Alternative Text)
<table>(<tr>(<td>...</td>)+</tr>)+</table>  | Table
<pre><code>...</code></pre>                 | Preformatted Code Block
<blockquote>...<blockquote>                 | Blockquote
<hr>                            | Horizontal Rule
<!-- ... -->                    | Comments

  Any tags missing? Let us know. Cheers

[1] https://github.com/writekit/quickrefs/blob/master/HTML.md
Gerald Bauer | 19 Jul 20:04 2015
Picon

New GitHub Org - /worldclassics - Free Great World Literature Books in .txt (that is, Markdown)

Hello,

  FYI: I've moved the two world classic (literature) books in Markdown
used for exampe by the static site generator's classics book theme /
template pack
to a new org for easy (re)use or summer beach reading.

    The first two classics are:

    - The Trial by Franz Kafka
    - Strange Case of Dr. Jekyll and Mr. Hyde by Robert Louis Stevenson

    More  <at>  https://github.com/worldclassics

   Cheers.
Gerald Bauer | 17 Jul 00:48 2015
Picon

New Static Site Theme for World (Literature) Classics in Markdown e.g. A Tale of Two Cities, The Trial, etc.

Hello,

  As a showcase I've converted a good old Gutenberg plain text world
(literature) classic to markdown.

   See the Strange Case of Dr. Jekyll and Mr. Hyde
   by Robert Louis Stevenson [1] as an example.

   Next I've put together a static site theme that lets you basically
drop all chapters into a _chapters folder and you're done, that is,
you get a great looking online live (e)book.

   See the Dr. Jekyll and Mr. Hyde live version (demo) [2]
   thanks to GitHub Pages (with built-in - surprise, surprise - Jekyll
processing ;-))

   And finally the ready-to-fork theme/template repo/source [3].

   Anyone else tried to convert world classics to Markdown
   for generating great looking books? Any insight appreciated.
Questions? Comments? Welcome.

   Cheers.

[1] https://github.com/writekit/classics--dr-jekyll-and-mr-hyde
[2] http://drjekyllthemes.github.io/jekyll-book-theme
[3] https://github.com/drjekyllthemes/jekyll-book-theme
Picon

markua -- a new flavor for long-form documents

some of you probably know that
leanpub.com has been creating
a new flavor targeted at books,
which they are calling "markua".

their in-progress documentation:
>   https://github.com/markuadoc/markua

here's a little javascript thing to
pull all of the chapters together:

>   http://zenmagiclove.com/simple/do-markua.html

that uses marky, brett terpstra's
rad web-based converter, which
in turn uses multimarkdown, so
the resultant .html will _not_ be
accurate according to markua...
but it will give you a rough idea.

>  http://markdownrules.com

-bowerbird
Alice Williams | 9 Jul 22:24 2015

Re: Markdown-Discuss Digest, Vol 148, Issue 3

Hi Everyone, thanks for the tips about anchor links. We discovered another issue that was not letting the anchor links work properly.

The anchor links do work with Fireball Markdown, our issue was related to admin login vs. customer login.

Sorry for the inconvenience .


On Thu, Jul 9, 2015 at 12:29 PM, <markdown-discuss-request <at> six.pairlist.net> wrote:
Send Markdown-Discuss mailing list submissions to
        markdown-discuss <at> six.pairlist.net

To subscribe or unsubscribe via the World Wide Web, visit
        https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
or, via email, send a message with subject or body 'help' to
        markdown-discuss-request <at> six.pairlist.net

You can reach the person managing the list at
        markdown-discuss-owner <at> six.pairlist.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Markdown-Discuss digest..."


Today's Topics:

   1. re: does fireball markdown support anchor links? (bowerbird)
   2. Re: does fireball markdown support anchor links? (Michel Fortin)
   3. How to create anchors in Fireball version of Markdown?(gitlab
      version links do not work) (Alice Williams)
   4. Re: How to create anchors in Fireball version of
      Markdown?(gitlab version links do not work) (Fletcher T. Penney)
   5. Re: does fireball markdown support anchor links?
      (Aristotle Pagaltzis)


----------------------------------------------------------------------

Message: 1
Date: Thu, 9 Jul 2015 04:39:45 -0400
From: bowerbird <bowerbird <at> aol.com>
To: markdown-discuss <at> six.pairlist.net, bowerbird <at> aol.com
Subject: re: does fireball markdown support anchor links?
Message-ID: <14e71f87563-70b0-69c4 <at> webprd-a52.mail.aol.com>
Content-Type: text/plain; charset=utf-8

david said:
>   Compare the manually specified
>   https://github.com/plaid/sanctuary#either
>   to the auto-generated
>   https://github.com/plaid/sanctuary#either--a---c---b---c---either-a-b---c

ok, first of all, if you manually specified this anchor:
>   https://github.com/plaid/sanctuary#either
no way ever would i expect it to go to that location.

especially since this link:
>   https://github.com/plaid/sanctuary#Either
goes to another location. (told you about case glitches.)

nope, i would expect your manually-specified link to
go to the location where this link actually goes:
>   https://github.com/plaid/sanctuary#either-type

(ironically, that header actually has a capital letter,
but the anchor is nonetheless in all-lowercase. ha.)

no, the thing about "manually specified" anchors
is that they will show all kinds of idiosyncrasies.
so not only are they work to create, but they are
also inconsistent, thus undependable, meaning
you have to look at each one to see what it is, so
they have almost _no_ redeeming qualities at all.

furthermore, the github methodology must be
doing some kind of javascript-based search
-- which is not a bad idea, as i suggested here:

>   https://medium.com/the-bower/lets-please-use-hashtag-terms-to-create-_arbitrary_-deep-links-f9185d5da2f0

(grok that deep-link! hyphens _and_ underbars!
and random crap at the end just to confuse you.)

except whatever github is doing is implemented
very strangely, so is certainly not what i would do.

however...

***

alan said:
>   If I were to pick a preferred format for auto-generated IDs,
>   it would have to be hyphens. Separating words is desirable
>   as it is more readable. And underscores, though not a terrible option,
>   can be obscured by underlines when the entire URL is presented to a user.

i disagree with several of those points.

but, hey, our own personal opinions don't mean jack.

i would gladly accept _any_ method, even if distasteful,
as long as everyone agreed that that's what we're doing.

so what would make a difference is if all the flavors
would converge on a mutual-agreed-upon method.

but...

>   Of course, I've been on this list too long to expect
>   implementations to actually converge on much of anything.

right, that's never gonna happen, i think we all know that.

so, then, what we need is to poll a million users or so, and
see which of the possible solutions they would most prefer,
and then let that vote guide us. but that won't happen either.

so the guiding principle is this:

if it _is_ broke, but you know you can't fix it,
don't waste time and energy by even trying.
don't even discuss it. pretend it doesn't exist.
(that's something all the flavor-makers can do!)

i would suggest we have reached this point.
thank you for your question, original-poster...

-bowerbird



------------------------------

Message: 2
Date: Thu, 9 Jul 2015 10:15:50 -0400
From: Michel Fortin <michel.fortin <at> michelf.ca>
To: "Discussion related to Markdown."
        <markdown-discuss <at> six.pairlist.net>
Subject: Re: does fireball markdown support anchor links?
Message-ID: <ABD97F73-1F3A-4D33-A42F-220A3CC01FAB <at> michelf.ca>
Content-Type: text/plain; charset="utf-8"

Le 2015-07-09 ? 0:30, Alan Hogan <contact <at> alanhogan.com> a ?crit :
> Furthermore, auto-gen'd headers *will* break when the text of the header is changed, which can be done for any number of innocuous reasons when we would like the link to be preserved. (Cool URIs don?t change, right?)
>
> For that reason, I have always been a fan of the ID specification syntax that pandoc, PHP Markdown Extra, maruku, kramdown, and a few others support:
>
>       ## This is a header         {#a-header}
>
> which compiles to:
>
>       <h2 id="a-header">This is a header</h2>
>
> Look at that! Cleaner Markdown *and* cleaner output than inserting your own <a> tag. And better, more future-proof section IDs than the auto-generated variety.
>
> Sadly, I never get to use it, due to the regrettable and totally predictable fact that so many Markdown converters ignore it.
>
> Not to pick on showdown, but look at its output:
> <h2 id="thisisaheaderaheader">This is a header {#a-header}</h2>

Yeah, this is sad.

I'll just point out that PHP Markdown Extra does support automatic generation of headers id as long as you provide it with a proper function to generate the id from the content of the header. For instance, you can configure the parser like this:

        $parser->header_id_func = function ($text) {
            return preg_replace('/[^a-z0-9]/', '-', strtolower($text));
        };

I'm not providing this function out of the box for a few reasons: 1. any specific algorithm to generate the id to is going to make some people complain about non-compatibility with another implementation, and 2. it's quite hard to come with something that'll work well with non-english text.

Just try it with accented characters and non-latin scripts and appreciate the nonsense. http://johnmacfarlane.net/babelmark2/?normalize=1&text=%23+English%0A%0A%23+Fran?ais%0A%0A%23+Espa?ol%0A%0A%23+?e?tina%0A%0A%23+???????%0A%0A%23+??%0A%0A%23+??%0A%0A%23+???????????%E2%80%8E%E2%80%8E%0A%0A%23+?????

Honestly, I find the {#a-header} approach better.

--
Michel Fortin
michel.fortin <at> michelf.ca
https://michelf.ca

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4939 bytes
Desc: not available
URL: <https://pairlist6.pair.net/pipermail/markdown-discuss/attachments/20150709/3da77f0a/attachment-0001.bin>

------------------------------

Message: 3
Date: Thu, 9 Jul 2015 11:56:40 -0700
From: Alice Williams <awilliams <at> machinezone.com>
To: markdown-discuss <at> six.pairlist.net
Subject: How to create anchors in Fireball version of Markdown?(gitlab
        version links do not work)
Message-ID:
        <CAFhkAKOBQEfR=fuwF3YHOOTKc7_xQVjYaXKQhw+i9bdj6NQAwA <at> mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi all,

Just curious if anyone knows how to get anchor links to work with Fireball
version of Markdown. (The Gitlab standard Markdown achieves anchor links
like this (but Fireball version does not support this format):

[link text](#anchor)

This anchor link does not work with Fireball version.

Does anyone know how to create Fireball Markdown anchors?

Thanks,
Alice
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist6.pair.net/pipermail/markdown-discuss/attachments/20150709/b8b044f2/attachment-0001.html>

------------------------------

Message: 4
Date: Thu, 09 Jul 2015 15:16:32 -0400
From: "Fletcher T. Penney" <fletcher <at> fletcherpenney.net>
To: "Discussion related to Markdown."
        <markdown-discuss <at> six.pairlist.net>
Subject: Re: How to create anchors in Fireball version of
        Markdown?(gitlab version links do not work)
Message-ID: <559EC890.4030903 <at> fletcherpenney.net>
Content-Type: text/plain; charset=windows-1252; format=flowed

I think you need to be more precise in your question.  I tried to flesh
it out in my prior response, but perhaps I failed.

The link you describe:

        [link text](#anchor)

works just fine in any version of Markdown.  It's just a regular link.

I suspect the problem you are having, as per my other message, is that
you need something for the link to "target."  If an anchor named
"#anchor" doesn't exist, that's a separate problem.


The various replies to your earlier message all suggested ways of
creating the necessary anchor that would work.

If those replies did not answer your question, then perhaps you could
more precisely specify the HTML output you are getting and the HTML
output you are expecting.


Fletcher



On 7/9/15 2:56 PM, Alice Williams wrote:
> Hi all,
>
> Just curious if anyone knows how to get anchor links to work with
> Fireball version of Markdown. (The Gitlab standard Markdown achieves
> anchor links like this (but Fireball version does not support this format):
>
> [link text](#anchor)
>
> This anchor link does not work with Fireball version.
>
> Does anyone know how to create Fireball Markdown anchors?
>
> Thanks,
> Alice
>
>
> _______________________________________________
> Markdown-Discuss mailing list
> Markdown-Discuss <at> six.pairlist.net
> https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
>

--
Fletcher T. Penney
fletcher <at> fletcherpenney.net


------------------------------

Message: 5
Date: Thu, 9 Jul 2015 21:29:37 +0200
From: Aristotle Pagaltzis <pagaltzis <at> gmx.de>
To: markdown-discuss <at> six.pairlist.net
Subject: Re: does fireball markdown support anchor links?
Message-ID: <20150709192937.GA97999 <at> plasmasturm.org>
Content-Type: text/plain; charset=utf-8

> the thing about "manually specified" anchors is that they will show
> all kinds of idiosyncrasies. so not only are they work to create, but
> they are also inconsistent, thus undependable, meaning you have to
> look at each one to see what it is, so they have almost _no_ redeeming
> qualities at all.

Yeah, totally agreed.

There are so many advantages to the fact that the anchor is dependably
derived from the text of the heading? well, between all the sites that
use the same Markdown processor configured in the same way? anyway, that
complete consistency is very useful.

It means that if you want to link to the heading, then all you have to
do is copy-paste the text of the heading and then manually edit it into
the format that the Markdown processor uses. You don?t need to look up
the anchor to copy-paste it, which would just be dumb.

It?s also a huge help if you want to know where a link goes ? you don?t
even need to click the link (who does that anyway?!), you just scroll
through the document from top to bottom while eyeballing the headers and
hey presto: you know *exactly* where it leads.

Furthermore, in the post-Web?2.0 era URIs are only cool if they could
potentially break before you notice that they are trending. So the fact
that links will break if you edit the text of a heading means derived
anchors are make cool URIs. Really cool URIs sometimes.

So it?s easy to show conclusively that derived anchors are perfect in
every way and the absolute idiosyncrasy of manually specified anchors
results in no redeeming qualities for them at all.


------------------------------

Subject: Digest Footer

_______________________________________________
Markdown-Discuss mailing list
Markdown-Discuss <at> six.pairlist.net
https://pairlist6.pair.net/mailman/listinfo/markdown-discuss


------------------------------

End of Markdown-Discuss Digest, Vol 148, Issue 3
************************************************

_______________________________________________
Markdown-Discuss mailing list
Markdown-Discuss <at> six.pairlist.net
https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
Alice Williams | 9 Jul 20:56 2015

How to create anchors in Fireball version of Markdown?(gitlab version links do not work)

Hi all,

Just curious if anyone knows how to get anchor links to work with Fireball version of Markdown. (The Gitlab standard Markdown achieves anchor links like this (but Fireball version does not support this format):

[link text](#anchor)

This anchor link does not work with Fireball version. 

Does anyone know how to create Fireball Markdown anchors? 

Thanks,
Alice
_______________________________________________
Markdown-Discuss mailing list
Markdown-Discuss <at> six.pairlist.net
https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
David Feitosa | 9 Jul 02:39 2015
Picon

Beamer and TOC

Hello,

I am trying to create a beamer presentation with a TOC,
but I not getting the end result with a TOC.
Instead, the presentation shows an empty page.

Is there something that I am doing wrong with it?

Here goes the code:

---
title: "Título"
author: "David"
output: 
  beamer_presentation:
    toc: true
header-includes:
- \usepackage[brazil]{babel}
colortheme: "dolphin"
---

# R Markdown 1

- A
- B
- C

# R Markdown 2

- A
- B
- C


Thanks in advance.

David F.
_______________________________________________
Markdown-Discuss mailing list
Markdown-Discuss <at> six.pairlist.net
https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
Alice Williams | 8 Jul 23:21 2015

does fireball markdown support anchor links?

Is there a way to get the same HTML anchor links like this:

<a href = "#anchorname">Link text</a>

<a name="anchorname"></a>

the gitlab version of markdown supports these links this way:

[link text](#anchor)

Heading <a name="anchor"></a>

but this does not work with fireball version of markdown.

thanks for any suggestions!
Alice
_______________________________________________
Markdown-Discuss mailing list
Markdown-Discuss <at> six.pairlist.net
https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
Picon

that's an endorsement

interesting to see asciidoctor.org
has this quote from linus torvalds...

>   Use AsciiDoc for document markup. 
>   Really.  It's actually readable by humans, 
>   easier to parse and way more flexible than XML.
>   — Linus Torvalds

-bowerbird

_______________________________________________
Markdown-Discuss mailing list
Markdown-Discuss <at> six.pairlist.net
https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
Picon

kudos and major props

david said:
>   I made something similar a few years ago

yes, you did indeed.

and i remember now thinking back then that it was brilliant.

you even anticipated the url-too-long problem by using bitly,
as well as combining several hashify into a single longer one.

and this reminds me that other people have also been using
the store-the-document-in-the-query-string approach recently.

but as far as i know, you were one of the first. so kudos for that.

do you know of any previous usage? if not, then major props...

and now that you've had some years to ponder this technique,
have you come up with any ideas for slick and inventive uses?

not that it needs any, it stands on its own just for being clever,
but if it has any additional functionality, i'd love to hear about it.

-bowerbird

Gmane