Convert Textile to ADOC
Max file size 100mb.
Textile vs ADOC Format Comparison
| Aspect | Textile (Source Format) | ADOC (Target Format) |
|---|---|---|
| Format Overview |
Textile
Textile Markup Language
Lightweight markup language originally developed by Dean Allen in 2002. Known for its use in Redmine, Textpattern CMS, and other web publishing tools. Offers a concise syntax for producing well-structured HTML with formatting, links, images, and tables. Lightweight Markup Web Publishing |
ADOC
AsciiDoc Document
Powerful lightweight markup language designed for writing documentation, articles, books, and technical content. Supports advanced features like includes, conditional processing, cross-references, and multiple output backends including HTML, PDF, and EPUB. Technical Docs Multi-Output |
| Technical Specifications |
Structure: Plain text with inline markup
Encoding: UTF-8 Format: Human-readable text markup Compression: None (plain text) Extensions: .textile |
Structure: Plain text with block/inline markup
Encoding: UTF-8 Format: Semantic document markup Compression: None (plain text) Extensions: .adoc, .asciidoc, .asc |
| Syntax Examples |
Textile markup syntax: h1. Main Heading *bold text* and _italic text_ # Ordered list item 1 # Ordered list item 2 |_. Header |_. Header | | Cell 1 | Cell 2 | |
AsciiDoc markup syntax: = Main Heading *bold text* and _italic text_ . Ordered list item 1 . Ordered list item 2 |=== | Header | Header | Cell 1 | Cell 2 |=== |
| Content Support |
|
|
| Advantages |
|
|
| Disadvantages |
|
|
| Common Uses |
|
|
| Best For |
|
|
| Version History |
Introduced: 2002 (Dean Allen)
Current Version: Textile 2 Status: Stable, limited development Evolution: Minor updates only |
Introduced: 2002 (Stuart Rackham)
Current Version: AsciiDoc / Asciidoctor 2.x Status: Actively maintained Evolution: Continuous improvements |
| Software Support |
Redmine: Native support
Textpattern: Built-in Pandoc: Read/write support Other: Limited editor support |
Asciidoctor: Full processing toolchain
GitHub: Native rendering Pandoc: Read/write support Other: IDE plugins (VS Code, IntelliJ) |
Why Convert Textile to ADOC?
Converting Textile documents to AsciiDoc (ADOC) format is an excellent choice when you need more powerful documentation features than Textile can provide. AsciiDoc offers advanced capabilities like include directives, conditional processing, cross-references, admonition blocks, and multi-format output that are essential for technical documentation and book publishing.
Textile, while a capable lightweight markup language, has a more limited feature set compared to AsciiDoc. As Textile adoption has declined in favor of Markdown and AsciiDoc, migrating to ADOC ensures your content remains accessible within a thriving ecosystem with active tooling support through Asciidoctor.
AsciiDoc is particularly well-suited for large, complex documents. Its include directive allows you to split content across multiple files and assemble them into a single document, making it ideal for book authoring, technical manuals, and collaborative documentation projects. The format also supports conditional processing, enabling you to produce different versions of a document from a single source.
The Asciidoctor toolchain can render ADOC files to HTML, PDF, EPUB, DocBook, and other formats, giving you far more output flexibility than Textile. GitHub natively renders .adoc files, making AsciiDoc a natural choice for project documentation hosted on GitHub.
Key Benefits of Converting Textile to ADOC:
- Advanced Features: Include directives, cross-references, admonitions, and conditional content
- Multi-Format Output: Generate HTML, PDF, EPUB, and DocBook from one source
- Active Ecosystem: Asciidoctor toolchain with regular updates and plugins
- GitHub Support: Native rendering of .adoc files on GitHub
- Book Publishing: Purpose-built for long-form technical content
- Modular Documents: Split large documents into reusable components
- Better Tooling: IDE support in VS Code, IntelliJ, and other editors
Practical Examples
Example 1: Heading and Text Formatting
Input Textile file (document.textile):
h1. Project Documentation h2. Introduction This is *bold text* and _italic text_. This has -strikethrough- text. bq. This is a blockquote with important information.
Output ADOC file (document.adoc):
= Project Documentation == Introduction This is *bold text* and _italic text_. This has [line-through]#strikethrough# text. [quote] ____ This is a blockquote with important information. ____
Example 2: Lists and Tables
Input Textile file (content.textile):
h2. Feature List # First ordered item # Second ordered item ## Nested item # Third item * Unordered item * Another item |_. Name |_. Role |_. Status | | Alice | Developer | Active | | Bob | Designer | Active |
Output ADOC file (content.adoc):
== Feature List . First ordered item . Second ordered item .. Nested item . Third item * Unordered item * Another item |=== | Name | Role | Status | Alice | Developer | Active | Bob | Designer | Active |===
Example 3: Links and Images
Input Textile file (links.textile):
h2. Resources Visit "our website":https://example.com for details. !images/logo.png(Company Logo)! p(note). This paragraph has a CSS class applied.
Output ADOC file (links.adoc):
== Resources Visit https://example.com[our website] for details. image::images/logo.png[Company Logo] [.note] This paragraph has a CSS class applied.
Frequently Asked Questions (FAQ)
Q: What is Textile markup?
A: Textile is a lightweight markup language developed by Dean Allen in 2002. It provides a concise syntax for producing well-structured HTML content and is notably used in Redmine project management, Textpattern CMS, and various blogging platforms. Textile uses notation like *bold*, _italic_, and h1. for headings.
Q: What is AsciiDoc (ADOC) format?
A: AsciiDoc is a powerful, human-readable document format designed for writing technical documentation, books, articles, and manuals. Files use the .adoc extension and are processed by tools like Asciidoctor to generate HTML, PDF, EPUB, and other output formats. AsciiDoc supports advanced features like includes, conditional content, cross-references, and admonition blocks.
Q: Will my Textile formatting be preserved in ADOC?
A: Yes, all common Textile formatting elements are preserved during conversion. Bold, italic, headings, lists, tables, links, images, and blockquotes all have direct equivalents in AsciiDoc. Some Textile-specific features like inline CSS classes may require minor adjustments, but the overall content and structure are faithfully converted.
Q: Why should I migrate from Textile to AsciiDoc?
A: AsciiDoc offers a significantly richer feature set including include directives, conditional processing, admonitions, cross-references, footnotes, and multi-format output. Its active ecosystem (Asciidoctor) provides better tooling, IDE support, and community resources. As Textile adoption continues to decline, migrating to AsciiDoc future-proofs your documentation.
Q: Can I use ADOC files on GitHub?
A: Yes! GitHub natively renders .adoc files, making AsciiDoc an excellent choice for project documentation, README files, and wikis hosted on GitHub. The rendering supports most AsciiDoc features including tables, code blocks, admonitions, and cross-references.
Q: How does Textile table syntax differ from AsciiDoc?
A: Textile uses pipe characters with |_. for header cells and | for data cells in a compact inline format. AsciiDoc uses a |=== delimiter to start and end tables, with cells separated by | characters. AsciiDoc tables support more advanced features like column spans, row spans, and nested content.
Q: What tools can process ADOC files?
A: The primary tool is Asciidoctor, available as a Ruby gem, JavaScript package (asciidoctor.js), and Java library. Asciidoctor can produce HTML5, PDF, EPUB3, DocBook, and other formats. IDE plugins are available for VS Code, IntelliJ IDEA, Atom, and other editors, providing live preview and syntax highlighting.
Q: Is AsciiDoc suitable for book publishing?
A: Absolutely! AsciiDoc was designed with book publishing in mind. O'Reilly Media uses AsciiDoc for many of their technical books. The format supports chapters, parts, appendices, index terms, bibliography, glossary, and all the structural elements needed for professional book production. Asciidoctor-pdf can generate print-ready PDFs.