[allura:tickets] #7987 Standardize fenced blocks in markdown

[Igor Bondarenko <je...@gmail.com>]

- **labels**: sf-current, sf-4 --> sf-current, sf-4, 42cc
- **status**: open --> in-progress
- **assigned_to**: Igor Bondarenko



---

** [tickets:#7987] Standardize fenced blocks in markdown**

**Status:** in-progress
**Milestone:** unreleased
**Labels:** sf-current sf-4 42cc 
**Created:** Mon Sep 14, 2015 05:18 PM UTC by Dave Brondsema
**Last Updated:** Mon Sep 21, 2015 03:49 PM UTC
**Owner:** Igor Bondarenko


Switch from our custom `FencedCodeProcessor` to the standard extension https://pythonhosted.org/Markdown/extensions/fenced_code_blocks.html so that we can support \`\`\` style, and so that blank lines are not needed before and after the `~~~~` blocks.  This will get us more closely aligned with the CommonMark standard, and the syntax highlighting of the markdown editor, and the 

However, the format for denoting the language inside the block is different there than the [CodeHilite](https://pythonhosted.org/Markdown/extensions/code_hilite.html) extension which we are already using (and our current `~~~~` uses as well since it simply makes an indented block).  So we'll have to figure out how to reconcile that.


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.