Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5B28610FBF for ; Mon, 14 Oct 2013 15:06:06 +0000 (UTC) Received: (qmail 13184 invoked by uid 500); 14 Oct 2013 15:06:06 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 13124 invoked by uid 500); 14 Oct 2013 15:06:05 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 13103 invoked by uid 99); 14 Oct 2013 15:06:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Oct 2013 15:06:03 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Oct 2013 15:05:59 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=a9WypuCiT3fLXyljTtL1jzmphv0btjBYgkoBsqbOCRI=; b=P1b4VK1xog5aerf1GDrPBQbyFinX7bOlPaAPU7u4ir1YvOdOFJ6MuHbjQPHroQQtDJHaKGQsoZkfwXRzOz+RhVhmFU6muhm4LI+JGEdNZQWGpslnmP/N6vv9PS0iVGYr8BM7hA1lGyJgtUh6rAJ5avZtOeDl9TL+y2QLHra6ldU=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-4.v29.ch3.sourceforge.com) by sfs-alluradaemon-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VVjiE-0006MT-NR for allura-dev@incubator.apache.org; Mon, 14 Oct 2013 15:05:38 +0000 Content-Type: multipart/related; boundary="===============0712664889630165912==" MIME-Version: 1.0 To: "[allura:tickets] " <6622@tickets.allura.p.re.sf.net> From: "Igor Bondarenko" Reply-To: "[allura:tickets] " <6622@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #6622 Convert or handle Github markdown extensions Message-ID:

Date: Mon, 14 Oct 2013 15:05:38 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============0712664889630165912== Content-Type: multipart/alternative; boundary="===============9141188523707677706==" MIME-Version: 1.0 --===============9141188523707677706== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit - **status**: in-progress --> code-review --- ** [tickets:#6622] Convert or handle Github markdown extensions** **Status:** code-review **Labels:** import github 42cc **Created:** Fri Aug 30, 2013 01:55 PM UTC by Dave Brondsema **Last Updated:** Tue Oct 01, 2013 11:02 AM UTC **Owner:** nobody When importing github content (tickets, wiki, comments) we should deal with their special markup. For example, code blocks with optional language specification: ~~~~ ```javascript function fancyAlert(arg) { if(arg) { $.facebox({div:'#foo'}) } } ``` ~~~~ should be converted to: 
~~~~
function fancyAlert(arg) {
  if(arg) {
    $.facebox({div:'#foo'})
  }
}
~~~~
And strikethrough `~~example~~` should be converted to `example`. This we could possibly support directly in our Markdown renderer if we wanted to. That would also allow it to work for Markdown files in git repos (since we won't modify those during import). Emoji I don't think we should handle (yet?) Cross-reference syntax https://help.github.com/articles/github-flavored-markdown#references we may want to consider handling. See also Trac syntax [#6140] handling. Converting markdown can be tricky to get right, so we have to be careful that we only convert the right content. Nested markup, escaped markup, etc. --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============9141188523707677706== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit
  • status: in-progress --> code-review

[tickets:#6622] Convert or handle Github markdown extensions

Status: code-review
Labels: import github 42cc
Created: Fri Aug 30, 2013 01:55 PM UTC by Dave Brondsema
Last Updated: Tue Oct 01, 2013 11:02 AM UTC
Owner: nobody

When importing github content (tickets, wiki, comments) we should deal with their special markup. For example, code blocks with optional language specification:

```javascript
function fancyAlert(arg) {
  if(arg) {
    $.facebox({div:'#foo'})
  }
}
```

should be converted to:

~~~~
function fancyAlert(arg) {
  if(arg) {
    $.facebox({div:'#foo'})
  }
}
~~~~

And strikethrough ~~example~~ should be converted to <s>example</s>. This we could possibly support directly in our Markdown renderer if we wanted to. That would also allow it to work for Markdown files in git repos (since we won't modify those during import).

Emoji I don't think we should handle (yet?)

Cross-reference syntax https://help.github.com/articles/github-flavored-markdown#references we may want to consider handling. See also Trac syntax [#6140] handling.

Converting markdown can be tricky to get right, so we have to be careful that we only convert the right content. Nested markup, escaped markup, etc.

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============9141188523707677706==-- --===============0712664889630165912==--