WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 4 years ago

#10250 closed defect (bug) (fixed)

switch wp.org markdown to markdown extra

Reported by: Denis-de-Bernardy Owned by: mdawaffe
Milestone: Priority: normal
Severity: normal Version:
Component: WordPress.org site Keywords:
Focuses: Cc:

Description

see http://wordpress.org/extend/plugins/sociable/changelog/

when you add foo_bar_foo, the _ get processed as italic.

whereas with markdown extra, they'd be treated like literal _.

Change History (7)

comment:1 Denis-de-Bernardy5 years ago

(switching the readme.txt file reader to markdown extra, that is.)

comment:2 Denis-de-Bernardy5 years ago

  • Cc markjaquith added

this plugin here needs to be changed accordingly:

http://wordpress-plugin-readme-parser.googlecode.com/svn/trunk/

comment:3 mdawaffe5 years ago

  • Owner changed from ryan to mdawaffe
  • Status changed from new to assigned

`foo_bar_foo` (with backticks) prevents the italics and encloses the string in <code> tags. Is that good enough? Where do you use underscores outside of snips (even one word snips) of code?

comment:4 Denis-de-Bernardy5 years ago

me, never. but I know markdown. not all users do, e.g.:

http://wordpress.org/extend/plugins/sociable/changelog/

comment:5 Denis-de-Bernardy5 years ago

see changelog for 3.2.2 in particular

switching to markdown extra works fine. michel does a great job at maintaining it.

comment:6 mdawaffe4 years ago

  • Status changed from assigned to accepted

comment:7 mdawaffe4 years ago

  • Resolution set to fixed
  • Status changed from accepted to closed

I've switched to Markdown Extra, so it should be used for new plugins. I'll go back and reparse all plugins shortly.

Note: See TracTickets for help on using tickets.