Opened 17 years ago
Closed 15 years ago
#7010 closed (wontfix)
Add MediaWiki style wikimarkup to django.contrib.markup
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Contrib apps | Version: | dev |
Severity: | Keywords: | markup | |
Cc: | Triage Stage: | Design decision needed | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
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)
Change History (6)
by , 17 years ago
Attachment: | wikimarkup.patch added |
---|
comment:1 by , 16 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Summary: | [PATCH] Add MediaWiki style wikimarkup to django.contrib.markup → Add MediaWiki style wikimarkup to django.contrib.markup |
comment:2 by , 16 years ago
Resolution: | wontfix |
---|---|
Status: | closed → reopened |
Triage Stage: | Unreviewed → 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 by , 16 years ago
Resolution: | → wontfix |
---|---|
Status: | reopened → 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 by , 15 years ago
Resolution: | wontfix |
---|---|
Status: | closed → reopened |
will not hurt, helps a lot!
comment:5 by , 15 years ago
Resolution: | → wontfix |
---|---|
Status: | reopened → 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.
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.