incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema" <>
Subject [allura:tickets] #6622 Convert or handle Github markdown extensions
Date Tue, 12 Nov 2013 22:27:40 GMT
Everything I've tested comes through fine.  One minor thing we should look at is if we can
support ``` without a blank line before it.  E.g. at

Github doesn't require a blank line before new types of blocks like code and lists.  A little
manual cleanup is probably ok, but since we're already handling ``` I think its worth trying
to add the blank line in automatically.  Not a big deal if its difficult, though.


** [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 Nov 12, 2013 07:45 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:

function fancyAlert(arg) {
  if(arg) {

should be converted to:

function fancyAlert(arg) {
  if(arg) {

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
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 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