You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Dave Brondsema <br...@users.sf.net> on 2013/09/09 19:50:25 UTC
[allura:tickets] #6610 Convert trac syntax better
- **Size**: --> 2
---
** [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 07:08 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.