Convert MediaWiki to Textile

Why Convert MediaWiki to Textile?

Converting MediaWiki markup to Textile format is valuable when migrating wiki content to platforms that use Textile as their primary markup language. Redmine, one of the most popular open-source project management tools, uses Textile for its wiki pages, issue descriptions, and documentation. If you have existing content on a MediaWiki platform and need to move it to Redmine, converting to Textile ensures your formatting transfers correctly.

MediaWiki and Textile are both lightweight markup languages, but they use fundamentally different syntax conventions. MediaWiki uses == headings ==, '''bold''', and {| table |} syntax, while Textile uses h2. headings, *bold*, and pipe-based table notation. Although both formats produce similar HTML output, the source markup is incompatible, making direct conversion necessary when switching between platforms that support different markup languages.

Textile offers several features that complement MediaWiki content well, including inline CSS class assignment, precise alignment control for text and images, and a more compact syntax for common formatting operations. Content creators working with Textpattern CMS or building styled web pages often prefer Textile for its ability to add HTML attributes directly within the markup without dropping into raw HTML.

The conversion process maps MediaWiki structural elements to their Textile equivalents: headings become h1. through h6. prefixed lines, bold and italic text use asterisk and underscore wrappers, lists maintain their hierarchical structure, and tables are reformatted using Textile's row and cell delimiters. Wiki-specific elements like categories, templates, and internal links are adapted or preserved as comments where no direct Textile equivalent exists.

Key Benefits of Converting MediaWiki to Textile:

• Redmine Migration: Move wiki content directly into Redmine projects and documentation
• CMS Integration: Use converted content in Textpattern and other Textile-based CMS platforms
• Compact Syntax: Textile offers shorter, more concise markup for common formatting
• CSS Styling: Apply CSS classes and inline styles directly within Textile markup
• HTML Quality: Textile generates clean, well-structured HTML output
• Project Documentation: Integrate wiki knowledge into project management workflows
• Content Portability: Move content between different markup ecosystems

Practical Examples

Example 1: Wiki Article to Redmine Page

Input MediaWiki file (project_guide.mediawiki):

== Project Setup Guide ==

'''Requirements:'''
* Python 3.10 or higher
* PostgreSQL database
* Redis for caching

=== Installation Steps ===
# Clone the repository
# Run {{Code|pip install -r requirements.txt}}
# Configure the database settings

{| class="wikitable"
|-
! Component !! Version !! Status
|-
| Python || 3.12 || Supported
|-
| Django || 5.0 || Required
|-
| PostgreSQL || 16 || Recommended
|}

Output Textile file (project_guide.textile):

h2. Project Setup Guide

*Requirements:*
* Python 3.10 or higher
* PostgreSQL database
* Redis for caching

h3. Installation Steps
# Clone the repository
# Run @pip install -r requirements.txt@
# Configure the database settings

|_. Component |_. Version |_. Status |
| Python | 3.12 | Supported |
| Django | 5.0 | Required |
| PostgreSQL | 16 | Recommended |

Example 2: Knowledge Base Migration

Input MediaWiki file (troubleshooting.mediawiki):

= Troubleshooting Guide =

== Common Issues ==

=== Error: Connection Refused ===
If you see ''connection refused'' errors:
# Check that the service is running
# Verify the '''port number''' is correct
# Ensure firewall rules allow the connection

See also: [[Network Configuration]]

{{Note|Always restart the service after configuration changes.}}

Output Textile file (troubleshooting.textile):

h1. Troubleshooting Guide

h2. Common Issues

h3. Error: Connection Refused
If you see _connection refused_ errors:
# Check that the service is running
# Verify the *port number* is correct
# Ensure firewall rules allow the connection

See also: "Network Configuration":Network_Configuration

p(note). Always restart the service after
configuration changes.

Example 3: Formatted Content with Tables

Input MediaWiki file (team_roster.mediawiki):

== Development Team ==

{| class="wikitable sortable"
|-
! Name !! Role !! Location
|-
| '''Alice Johnson''' || Lead Developer || New York
|-
| '''Bob Smith''' || Backend Engineer || London
|-
| '''Carol Lee''' || Frontend Developer || Tokyo
|}

''Last updated: January 2026''

Output Textile file (team_roster.textile):

h2. Development Team

|_. Name |_. Role |_. Location |
| *Alice Johnson* | Lead Developer | New York |
| *Bob Smith* | Backend Engineer | London |
| *Carol Lee* | Frontend Developer | Tokyo |

_Last updated: January 2026_

Frequently Asked Questions (FAQ)

Q: What is Textile markup?

A: Textile is a lightweight markup language created by Dean Allen in 2002 that converts plain text into structured HTML. It uses concise notation like h2. for headings, *bold* for bold text, _italic_ for italic, and pipe-based table syntax. Textile is the default markup language in Redmine project management software and Textpattern CMS.

Q: Will my MediaWiki formatting be preserved in Textile?

A: Yes, most structural formatting converts accurately. Headings, bold, italic, lists, tables, and links all have direct Textile equivalents. However, MediaWiki-specific features like categories ([[Category:...]]), templates, transclusion, and magic words do not have Textile counterparts and will be simplified or preserved as comments during conversion.

Q: Can I use the converted Textile in Redmine?

A: Absolutely! The output Textile markup is fully compatible with Redmine's wiki system. You can paste the converted content directly into Redmine wiki pages, issue descriptions, or project documentation. Redmine's built-in Textile renderer will display the formatting correctly.

Q: How are MediaWiki tables converted to Textile?

A: MediaWiki tables ({| class="wikitable" ... |}) are converted to Textile's pipe-based table format. Header cells (! in MediaWiki) become |_. cells in Textile, and regular cells use simple | delimiters. Complex table attributes like colspan, rowspan, and custom styling are preserved where Textile supports them.

Q: What happens to MediaWiki templates during conversion?

A: MediaWiki templates (e.g., Infobox, Navbox, Citation) do not have direct Textile equivalents since Textile does not support a template system. Template content is either expanded to its visible text representation or noted as a comment in the Textile output so you can manually adapt it to your target platform.

Q: How are internal wiki links handled?

A: MediaWiki internal links ([[Page Name]] or [[Page|Display Text]]) are converted to Textile hyperlinks using the "Display Text":URL format. Since Textile does not have a native wiki linking mechanism, the links are converted to standard URL references that can be adjusted for your target platform.

Q: Is Textile still actively used?

A: While Textile has a smaller community than Markdown, it remains actively used in several important platforms. Redmine, which is used by many organizations for project management, relies on Textile for its wiki and documentation features. Textpattern CMS also uses Textile natively. The format is stable and well-supported in its primary ecosystems.

Q: Can I convert multiple MediaWiki files to Textile at once?

A: Yes! Our converter supports batch processing. Upload multiple MediaWiki files simultaneously, and each will be independently converted to Textile format. This is especially useful when migrating an entire wiki to a Redmine-based project documentation system.