Code

Opened 6 years ago

Closed 4 years ago

#7010 closed (wontfix)

Add MediaWiki style wikimarkup to django.contrib.markup

Reported by: Joshua "jag" Ginsberg <jag@…> Owned by: nobody
Component: Contrib apps Version: master
Severity: Keywords: markup
Cc: Triage Stage: Design decision needed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

>>> from django.contrib.markup.templatetags import markup
>>> s = u"""=WikiMarkup=
... 
... A popular markup format is the one used by MediaWiki. It's particularly easy for non-technical users to use.
... 
... * It supports '''bold''', ''italic'' text easily. 
... ** Oh yeah. Lists too. 
... * Its code can be downloaded from [http://code.google.com/p/wikimarkup/] 
... 
... This patch adds MediaWiki-style wiki markup to Django.
... """
>>> markup.wikimarkup(s)
u'<h1 id="w_wikimarkup">WikiMarkup</h1>\n<p>A popular markup format is the one used by MediaWiki. It\'s particularly easy for non-technical users to use.\n</p>\n<ul><li> It supports <b>bold</b> and <i>italic</i> text easily.\n<ul><li> Oh yeah. Lists too.\n</li></ul>\n</li><li> Its code can be downloaded from <a href="http://code.google.com/p/wikimarkup/">http://code.google.com/p/wikimarkup/</a>\n</li></ul>\n<p>This patch adds MediaWiki-style wiki markup to Django.\n</p>'

Attachments (1)

wikimarkup.patch (1.3 KB) - added by Joshua "jag" Ginsberg <jag@…> 6 years ago.

Download all attachments as: .zip

Change History (6)

Changed 6 years ago by Joshua "jag" Ginsberg <jag@…>

comment:1 Changed 6 years ago by Simon Greenhill

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to wontfix
  • Status changed from new to closed
  • Summary changed from [PATCH] Add MediaWiki style wikimarkup to django.contrib.markup to Add MediaWiki style wikimarkup to django.contrib.markup

Hmm.. nice patch Jag, but I'm not sure that we want to fill Django up with markup engines. I'm going to mark this as wontfix, but if someone really disagrees with me, please reopen this ticket with design-decision-needed.

comment:2 Changed 6 years ago by programmerq

  • Resolution wontfix deleted
  • Status changed from closed to reopened
  • Triage Stage changed from Unreviewed to Design decision needed

I would venture to say that it is a good idea to include additional markup engines:

Currently there isn't a straightforward way to add your own engines. You would have to patch django or copy the markup filter code to your project and rework it that way. This seems a bit clumsy, and in time would create duplicate efforts among various developers. What do the core developers think?

comment:3 Changed 6 years ago by ubernostrum

  • Resolution set to wontfix
  • Status changed from reopened to closed

A third-party solution is already available which provides a generic system for supporting arbitrary markup schemes through template filters, so I'd be inclined to leave this at wontfix.

comment:4 Changed 4 years ago by haras

  • Resolution wontfix deleted
  • Status changed from closed to reopened

will not hurt, helps a lot!

comment:5 Changed 4 years ago by kmtracey

  • Resolution set to wontfix
  • Status changed from reopened to closed

Please don't reopen tickets closed wontfix, please see http://docs.djangoproject.com/en/dev/internals/contributing/#id1, which notes what you should do in cases where you disagree with such a decision.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.