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 3ECFF10D7A for ; Tue, 27 Aug 2013 19:08:47 +0000 (UTC) Received: (qmail 39006 invoked by uid 500); 27 Aug 2013 19:08:47 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 38939 invoked by uid 500); 27 Aug 2013 19:08:44 -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 38931 invoked by uid 99); 27 Aug 2013 19:08:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Aug 2013 19:08:43 +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, 27 Aug 2013 19:08:37 +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=fEARj0FiHijnnOsEl85kwjMQ0mWD68HsuijxylJuFws=; b=r/GmfhF5QLI7FerlQSrhr3n0gGsgMVRUaAA5UpTfgfTqAUazXU2PJJn9ktb0c3/GAA41AOiYMk546FNEtS1eS0z26/l3sBs60XT9d7MVDvfkgNRB7UF8sx7WNRE/5gucRQjN1PqiVs1/HCmlhGOTj0XzM1n3ygfg8UOVlrm2YXE=; 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 1VEOci-0001Tr-Iz for allura-dev@incubator.apache.org; Tue, 27 Aug 2013 19:08:16 +0000 Content-Type: multipart/related; boundary="===============6197935591778001694==" MIME-Version: 1.0 To: "[allura:tickets] " <6610@tickets.allura.p.re.sf.net> From: "Dave Brondsema" Reply-To: "[allura:tickets] " <6610@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #6610 Convert trac syntax better Message-ID:

Date: Tue, 27 Aug 2013 19:08:16 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============6197935591778001694== Content-Type: multipart/alternative; boundary="===============1969164376563835015==" MIME-Version: 1.0 --===============1969164376563835015== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit - **summary**: Convert trac heading syntax == --> Convert trac syntax better - Description has changed: Diff: ~~~~ --- old +++ new @@ -1 +1,12 @@ -Trac syntax for headings, e.g. `== NOTE ==` is not converted in the Trac ticket export/import process. +The Trac ticket export/import process doesn't handle the following syntax correctly: + +* headings e.g. `== NOTE ==` +* preformatted blocks, using `{{{ ... }}}` -- this does seem to come through OK in comments, presumably because we're converting those differently +* lists that have no blank line preceding them, e.g. `blah blah\n* foo\n* bar` +* https://sourceforge.net/apps/trac/gfarm/ticket/594#comment:5 gets a `\n` incorrectly introduced between "merged into" and "2.6 branch" +* `----` for a horizontal line becomes a markdown heading if there is no blank line before it +* special characters that Markdown might interpret need to be escaped. Simple example: `foo bar` Perhaps helpers.plain2markdown() will help. +* Make sure external links like `[http://google.com test]` work (I'm not sure) + + +These are the issues I noticed - look through the Trac syntax reference to see if there are more. ~~~~ --- ** [tickets:#6610] Convert trac syntax better** **Status:** open **Labels:** trac import **Created:** Tue Aug 27, 2013 06:45 PM UTC by Dave Brondsema **Last Updated:** Tue Aug 27, 2013 06:45 PM UTC **Owner:** nobody The Trac ticket export/import process doesn't handle the following syntax correctly: * headings e.g. `== NOTE ==` * preformatted blocks, using `{{{ ... }}}` -- this does seem to come through OK in comments, presumably because we're converting those differently * lists that have no blank line preceding them, e.g. `blah blah\n* foo\n* bar` * https://sourceforge.net/apps/trac/gfarm/ticket/594#comment:5 gets a `\n` incorrectly introduced between "merged into" and "2.6 branch" * `----` for a horizontal line becomes a markdown heading if there is no blank line before it * special characters that Markdown might interpret need to be escaped. Simple example: `foo bar` Perhaps helpers.plain2markdown() will help. * Make sure external links like `[http://google.com test]` work (I'm not sure) These are the issues I noticed - look through the Trac syntax reference to see if there are more. --- 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. --===============1969164376563835015== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit
  • summary: Convert trac heading syntax == --> Convert trac syntax better
  • Description has changed:

Diff:

--- old
+++ new
@@ -1 +1,12 @@
-Trac syntax for headings, e.g. `== NOTE ==` is not converted in the Trac ticket export/import process.
+The Trac ticket export/import process doesn't handle the following syntax correctly:
+
+* headings e.g. `== NOTE ==`
+* preformatted blocks, using `{{{ ... }}}` -- this does seem to come through OK in comments, presumably because we're converting those differently
+* lists that have no blank line preceding them, e.g. `blah blah\n* foo\n* bar`
+* https://sourceforge.net/apps/trac/gfarm/ticket/594#comment:5 gets a `\n` incorrectly introduced between "merged into" and "2.6 branch"
+* `----` for a horizontal line becomes a markdown heading if there is no blank line before it
+* special characters that Markdown might interpret need to be escaped.  Simple example: `foo <a b c> bar`  Perhaps helpers.plain2markdown() will help.
+* Make sure external links like `[http://google.com test]` work (I'm not sure) 
+
+
+These are the issues I noticed - look through the Trac syntax reference to see if there are more.

[tickets:#6610] Convert trac syntax better

Status: open
Labels: trac import
Created: Tue Aug 27, 2013 06:45 PM UTC by Dave Brondsema
Last Updated: Tue Aug 27, 2013 06:45 PM UTC
Owner: nobody

The Trac ticket export/import process doesn't handle the following syntax correctly:

  • headings e.g. == NOTE ==
  • preformatted blocks, using {{{ ... }}} -- this does seem to come through OK in comments, presumably because we're converting those differently
  • lists that have no blank line preceding them, e.g. blah blah\n* foo\n* bar
  • https://sourceforge.net/apps/trac/gfarm/ticket/594#comment:5 gets a \n incorrectly introduced between "merged into" and "2.6 branch"
  • ---- for a horizontal line becomes a markdown heading if there is no blank line before it
  • special characters that Markdown might interpret need to be escaped. Simple example: foo <a b c> bar Perhaps helpers.plain2markdown() will help.
  • Make sure external links like [http://google.com test] work (I'm not sure)

These are the issues I noticed - look through the Trac syntax reference to see if there are more.

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.

--===============1969164376563835015==-- --===============6197935591778001694==--