Convert Textile to MediaWiki

Why Convert Textile to MediaWiki?

Converting Textile markup to MediaWiki format is essential when migrating content from Redmine or Textpattern to wiki-based platforms powered by MediaWiki software. MediaWiki is the engine behind Wikipedia, the world's largest encyclopedia, and is widely deployed for corporate wikis, knowledge management systems, and collaborative documentation platforms.

Both Textile and MediaWiki are markup languages, but they use significantly different syntax conventions. Textile uses "h1." for headings while MediaWiki uses "= Heading =" with equals signs. Textile bold is *bold* while MediaWiki uses '''bold''' with triple apostrophes. Link syntax, table notation, and list formatting all differ between the two formats.

MediaWiki offers powerful features not available in Textile, including a template system for reusable content blocks, categories for organizing pages, namespaces for content separation, and a robust citation and reference system. Converting to MediaWiki format gives your content access to these collaborative features.

This conversion is particularly valuable for organizations that maintain both Redmine for project management and MediaWiki for internal documentation. By converting Textile content to MediaWiki syntax, you can consolidate documentation into your wiki platform, enabling collaborative editing, version history, and structured knowledge management.

Key Benefits of Converting Textile to MediaWiki:

• Wiki Platform Migration: Move Redmine content to MediaWiki-based systems
• Wikipedia Compatibility: Use content on Wikipedia and Wikimedia projects
• Template System: Access MediaWiki's powerful template functionality
• Collaborative Editing: Enable multi-user editing with version tracking
• Category Support: Organize content with MediaWiki categories
• Citation System: Use MediaWiki's built-in reference management
• Knowledge Management: Consolidate documentation in a wiki platform

Practical Examples

Example 1: Documentation Page Migration

Input Textile file (docs.textile):

h1. Server Architecture

h2. Overview

The system uses a *microservices* architecture
with _three main components_:

* API Gateway
* Authentication Service
* Data Processing Engine

h2. Requirements

# Install Docker
# Configure network
# Deploy containers

Output MediaWiki file (docs.wiki):

= Server Architecture =

== Overview ==

The system uses a '''microservices''' architecture
with ''three main components'':

* API Gateway
* Authentication Service
* Data Processing Engine

== Requirements ==

# Install Docker
# Configure network
# Deploy containers

Example 2: Table and Link Conversion

Input Textile file (specs.textile):

h2. API Endpoints

|_. Method |_. Endpoint |_. Description |
| GET | /api/users | List all users |
| POST | /api/users | Create new user |
| DELETE | /api/users/:id | Delete user |

See "API Reference":http://docs.example.com for details.

!architecture.png!

Output MediaWiki file (specs.wiki):

== API Endpoints ==

{| class="wikitable"
|-
! Method !! Endpoint !! Description
|-
| GET || /api/users || List all users
|-
| POST || /api/users || Create new user
|-
| DELETE || /api/users/:id || Delete user
|}

See [http://docs.example.com API Reference] for details.

[[File:architecture.png]]

Example 3: Formatted Content Migration

Input Textile file (guide.textile):

h1. Quick Start Guide

h2. Step 1: Installation

Install the package using @pip@:

bc. pip install mypackage
python setup.py configure

h2. Step 2: Configuration

bq. Important: Always back up your
configuration before making changes.

Set these *required* fields:
* @database_url@ - Database connection string
* @secret_key@ - Application secret

Output MediaWiki file (guide.wiki):

= Quick Start Guide =

== Step 1: Installation ==

Install the package using pip:

pip install mypackage
python setup.py configure


== Step 2: Configuration ==

Important: Always back up your
configuration before making changes.

Set these '''required''' fields:
* database_url - Database connection string
* secret_key - Application secret

Frequently Asked Questions (FAQ)

Q: What is MediaWiki markup?

A: MediaWiki markup is the formatting language used by MediaWiki software, which powers Wikipedia and thousands of other wikis. It uses equals signs for headings, triple apostrophes for bold, double apostrophes for italic, and special syntax for tables, links, and templates. It is the most widely used wiki markup language in the world.

Q: How are Textile headings converted to MediaWiki?

A: Textile headings like "h1. Title" are converted to MediaWiki's equals-sign syntax: "= Title =". Similarly, "h2." becomes "== Title ==", "h3." becomes "=== Title ===", and so on. The heading level is preserved exactly during conversion.

Q: Are Textile tables properly converted to MediaWiki tables?

A: Yes, Textile pipe-delimited tables are converted to MediaWiki's table syntax using {| class="wikitable" ... |}. Header cells (|_. in Textile) become !! cells in MediaWiki, and regular cells use || notation. The table structure and content are fully preserved.

Q: Can I use the converted content directly on Wikipedia?

A: The converted MediaWiki syntax is compatible with Wikipedia's editing format. However, Wikipedia has specific content guidelines, notability requirements, and citation standards that must be met independently. The conversion handles the syntax translation, but editorial compliance is separate.

Q: How are Textile links converted to MediaWiki links?

A: Textile external links like "text":http://url become MediaWiki external links [http://url text]. Internal wiki links can be represented using double brackets in MediaWiki. The converter handles both external and internal link formats appropriately.

Q: What happens to Textile code blocks in MediaWiki?

A: Textile inline code (@code@) is converted to MediaWiki's code tags. Block code sections (bc. in Textile) are converted to

...

Q: Does MediaWiki support Textile's inline CSS features?

A: MediaWiki has its own styling approach using CSS classes, inline styles, and templates. Textile's inline CSS classes (like p(classname). text) don't have a direct equivalent in standard MediaWiki markup, but similar styling can be achieved using MediaWiki's {{style}} templates or inline HTML attributes.

Q: Can I convert MediaWiki back to Textile?

A: Yes, our platform supports bidirectional conversion between Textile and MediaWiki formats. This is useful when you need to move content between Redmine and MediaWiki-based platforms in either direction.