Opened 17 years ago
Closed 17 years ago
#10250 closed defect (bug) (fixed)
switch wp.org markdown to markdown extra
| Reported by: | Denis-de-Bernardy | Owned by: | mdawaffe |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | WordPress.org Site | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
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)
#2
@
17 years ago
- Cc added
this plugin here needs to be changed accordingly:
http://wordpress-plugin-readme-parser.googlecode.com/svn/trunk/
#3
@
17 years ago
- Owner changed from to
- Status new → 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?
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
(switching the readme.txt file reader to markdown extra, that is.)