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 C70F610C0A for ; Tue, 12 Nov 2013 22:28:28 +0000 (UTC) Received: (qmail 73779 invoked by uid 500); 12 Nov 2013 22:28:28 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 73758 invoked by uid 500); 12 Nov 2013 22:28:28 -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 73750 invoked by uid 99); 12 Nov 2013 22:28:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Nov 2013 22:28:28 +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 (nike.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; Tue, 12 Nov 2013 22:28:23 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:References:In-Reply-To:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=iwFtJ5TMMuhKTwwgQIoTLs7Z6K+XZmEhGAHB0v3SIBw=; b=q/o/BYrmDRjHs3DdAvUfGvQFzjDE6vp2oz82RHGrmxY9UlpSSX8VAzMKJ/ePBX1/qU6C5WowgayUKwmpE3rByLkLUozNijrMjhGauerGdRjHijakLO0eczqcJB7oLfs4ARohh5Xl9DSUoPtJ6CV+s08vYvjuFkoAviD/qchOGbI=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-2.v29.ch3.sourceforge.com) by sfs-alluradaemon-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VgMRF-0002ss-Vo for allura-dev@incubator.apache.org; Tue, 12 Nov 2013 22:28:02 +0000 Content-Type: multipart/related; boundary="===============1122638156827167594==" MIME-Version: 1.0 To: allura-dev@incubator.apache.org From: "Dave Brondsema" Reply-To: "[allura:tickets] " <6622@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #6622 Convert or handle Github markdown extensions Message-ID:

In-Reply-To: <5220a44ac4d1046500a8cd98.tickets@allura.p.sourceforge.net> References: <5220a44ac4d1046500a8cd98.tickets@allura.p.sourceforge.net> Date: Tue, 12 Nov 2013 22:28:01 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============1122638156827167594== Content-Type: multipart/alternative; boundary="===============6515018705392647548==" MIME-Version: 1.0 --===============6515018705392647548== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit - **status**: code-review --> in-progress --- ** [tickets:#6622] Convert or handle Github markdown extensions** **Status:** in-progress **Labels:** import github 42cc **Created:** Fri Aug 30, 2013 01:55 PM UTC by Dave Brondsema **Last Updated:** Tue Nov 12, 2013 10:27 PM 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. --===============6515018705392647548== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit
  • status: code-review --> in-progress

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

Status: in-progress
Labels: import github 42cc
Created: Fri Aug 30, 2013 01:55 PM UTC by Dave Brondsema
Last Updated: Tue Nov 12, 2013 10:27 PM 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.

--===============6515018705392647548==-- --===============1122638156827167594==--