Feature Proposal: Is it difficult to support Wikipedia:AsciiDoc

Motivation

We already support LaTeX, and most of the markup of Mediawiki and what happened to the WikiCreole initiative? Why not support yet another lightweight markup language?

Description and Documentation

AsciiDoc comes with a "converter program" that can convert AsciiDoc documents to XHTML, DocBook or HTML, so its integration should be pretty easy. There are also Matplotlib AsciiDoc and Graphviz filters available.

Any developer interested in implementing a AsciiDocPlugin/Contrib whatever?

Examples

Impact

WhatDoesItAffect:

Implementation

-- Contributors: FranzJosefGigler - 05 Nov 2012

Discussion

It looks very well thought out. I like it. But personally I'm still trying to find the time to think more about FoswikiDOM first though.

There are also issues with WYSIWYG; and without a FoswikiDOM it will be hard to mix content from one markup or another all on the same page. And how to handle macro expansion; and whether the AsciiDoc markup participates in ->renderTML. It's possible, it just depends what level of integration you desire.

  • Do you just want a TML<->AsciiDoc converter?
  • Do you desire that Topic.txt files are stored with AsciiDoc markup?
  • Perhaps Topic.txt still stores TML but we do some sort of crude TML<->AsciiDoc markup translation in the before/after edit handlers?
  • Perhaps something easier, just a new <asciidoc>...</asciidoc> or %ASCIIDOC%...%ENDASCIIDOC% tag in a similar way to how latex is handled?

-- PaulHarvey - 05 Nov 2012

I thought about the last one for the beginning. Mark the text that should be interpreted by the asciidoc script somehow and let that script do the work and show the resulting HTML. Maybe add a generated DocBook-version of the content as hidden attachment for later reuse. Thus one could use Foswiki macros within AsciiDoc blocks to get the best of both worlds.

-- FranzJosefGigler - 06 Nov 2012

Parking this until a developer comes along.

-- GeorgeClark - 13 Feb 2016
 
Topic revision: r4 - 13 Feb 2016, GeorgeClark
The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License    Legal Imprint    Privacy Policy