incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema" <>
Subject [allura:tickets] #6610 Convert trac syntax better
Date Wed, 16 Oct 2013 18:28:26 GMT
There's over-escaping in
 Or maybe it's linkifying of #123 ticket references, which ideally wouldn't happen within
pre-formatted text (`<code>` and `<pre>`).  html2text does that type of recognition
(see its `handle_data`).  Maybe we could hook into the `escape_md_section` call and only replace
links there? 

Can "Originally posted by:" in comments be italicized like is done for ticket body?


** [tickets:#6610] Convert trac syntax better**

**Status:** in-progress
**Labels:** trac import 
**Created:** Tue Aug 27, 2013 06:45 PM UTC by Dave Brondsema
**Last Updated:** Wed Oct 16, 2013 05:26 PM UTC
**Owner:** Tim Van Steenburgh

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`
* 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
* 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 `[ test]` work (I'm not sure) 

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


Sent from because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message