Convert ADOC to TEXTILE

Drag and drop files here or click to select.
Max file size 100mb.

Uploading progress:

ADOC vs TEXTILE Format Comparison

Aspect	ADOC (Source Format)	TEXTILE (Target Format)
Format Overview	ADOC AsciiDoc Markup Language Lightweight markup language designed for writing technical documentation, books, and articles with human-readable plain text syntax. Created by Stuart Rackham in 2002. Supports multiple output formats and is popular for documentation-as-code workflows. Plain Text Technical Docs	TEXTILE Textile Markup Language Simple markup language designed for web content creation with intuitive syntax that converts easily to HTML. Created by Dean Allen in 2002. Known for its use in Redmine project management and wiki platforms. Focuses on readability and quick web publishing. Web Content Redmine Native
Technical Specifications	Structure: Plain text with semantic markup Encoding: UTF-8 text Format: Human-readable markup Compression: None (plain text) Extensions: .adoc, .asciidoc, .asc	Structure: Plain text with minimal markup Encoding: UTF-8 text Format: Paragraph-based markup Compression: None (plain text) Extensions: .textile
Syntax Examples	AsciiDoc uses semantic markup: = Document Title Author Name == Section Heading This is a bold and _italic_ text. * List item one * List item two [source,python] ---- print("Hello World") ----	Textile uses simple punctuation: h1. Document Title h2. Section Heading This is a bold and _italic_ text. * List item one * List item two <pre><code> print("Hello World") </code></pre>
Content Support	Multi-level headings and sections Bold, italic, monospace formatting Ordered and unordered lists Tables with complex layouts Source code blocks with highlighting Admonitions (NOTE, TIP, WARNING) Cross-references and links Images and diagrams Include directives Conditional content	Headers (h1. through h6.) Bold, italic, underline formatting Ordered and unordered lists Basic tables with pipe syntax Code blocks (pre/code tags) Block quotes Links and images Inline HTML support CSS class/ID application Footnotes
Advantages	Human-readable plain text Rich feature set for documentation Version control friendly (Git) Multi-format output (HTML, PDF, DOCX) Strong tooling ecosystem Excellent for technical content Powerful include and conditional directives	Very simple to learn Quick to write Native Redmine integration Clean readable source Direct XHTML output Inline HTML when needed CSS class support
Disadvantages	More complex syntax for advanced features Requires learning attribute system Overkill for simple content Less familiar to general users Requires toolchain for conversion	Limited formatting options No native code highlighting Fewer output format options Less active development Limited to web publishing mainly
Common Uses	Software documentation Technical manuals and guides API documentation Books and ebooks README files and wikis Knowledge bases	Redmine wikis and issues Web content management Blog posts Simple documentation Wiki pages Project tracking notes
Best For	Technical writers and developers Documentation-as-code projects Multi-output publishing Version-controlled documentation	Redmine users and administrators Web content creators Project management wikis Teams needing simple markup
Version History	Introduced: 2002 (Stuart Rackham) Current Version: Asciidoctor 2.x Status: Active development Evolution: Asciidoctor (2013) modernized	Introduced: 2002 (Dean Allen) Current Version: Textile 2.0 spec Status: Maintenance mode Evolution: RedCloth Ruby library
Software Support	Asciidoctor: Primary processor (Ruby/JS/Java) Editors: VS Code, IntelliJ, Atom Preview: Browser extensions available Other: GitHub, GitLab, Antora	Redmine: Built-in native support RedCloth: Ruby library for processing Textpattern: CMS with Textile support Other: Various wiki platforms

Why Convert ADOC to TEXTILE?

Converting AsciiDoc to Textile is particularly valuable when you need to share content with teams using Redmine or other Textile-based platforms. While AsciiDoc provides comprehensive technical documentation capabilities, Textile offers a simpler, more accessible format that integrates natively with popular project management tools.

Textile is the default markup language for Redmine wikis and issue descriptions, making it essential for development teams using this project management platform. By converting your AsciiDoc documentation to Textile, you can seamlessly integrate technical content into your Redmine projects without requiring team members to learn AsciiDoc syntax.

The conversion enables you to leverage your existing AsciiDoc content in wikis, issue trackers, and web publishing systems that support Textile markup. This is particularly useful for organizations that maintain technical documentation in AsciiDoc but need to publish content to Textile-based platforms for broader team access.

Textile's simpler syntax makes it ideal for collaborative editing scenarios where not all contributors are familiar with more complex markup languages. The conversion preserves your content structure while adapting it to Textile's straightforward formatting conventions, ensuring readability and editability for all team members.

Key Benefits of Converting ADOC to TEXTILE:

Redmine Integration: Native support in Redmine wikis and issues
Simplified Collaboration: Easier for non-technical team members
Web Publishing Ready: Direct conversion to clean XHTML
Wiki Compatibility: Works with many wiki platforms
Lighter Syntax: Minimal markup for simple documents
Project Documentation: Ideal for project wikis and notes
Legacy System Support: Compatible with older CMS platforms

Practical Examples

Example 1: Document Headers and Text Formatting

Input AsciiDoc file (project.adoc):

= Project Documentation
Author Name
:toc:

== Introduction

This is a *bold statement* about our project.
We use _italic text_ for emphasis and
`monospace` for code references.

=== Background

The project started in 2023 with the goal of
improving team collaboration.

==== Technical Details

We implemented several key features:

. First feature
. Second feature
. Third feature

Output TEXTILE file (project.textile):

h1. Project Documentation

h2. Introduction

This is a *bold statement* about our project.
We use _italic text_ for emphasis and
@monospace@ for code references.

h3. Background

The project started in 2023 with the goal of
improving team collaboration.

h4. Technical Details

We implemented several key features:

# First feature
# Second feature
# Third feature

Example 2: Tables and Lists for Project Tracking

Input AsciiDoc file (sprint.adoc):

== Sprint Overview

.Sprint 15 Task Status
[cols="2,1,1,3", options="header"]
|===
|Task |Assignee |Status |Notes

|API Development |John |Done |Completed ahead of schedule
|UI Components |Sarah |In Progress |80% complete
|Testing |Mike |Pending |Waiting for API
|===

=== Priority Items

* Complete API endpoints
* Finish UI components
* Run integration tests

WARNING: Database migration pending approval

Output TEXTILE file (sprint.textile):

h2. Sprint Overview

*Sprint 15 Task Status*

|_.Task|_.Assignee|_.Status|_.Notes|
|API Development|John|Done|Completed ahead of schedule|
|UI Components|Sarah|In Progress|80% complete|
|Testing|Mike|Pending|Waiting for API|

h3. Priority Items

* Complete API endpoints
* Finish UI components
* Run integration tests

*Warning:* Database migration pending approval

Example 3: Links, Images, and Code Blocks

Input AsciiDoc file (resources.adoc):

== Resources

Visit our https://example.com[project website] for
more information.

See the link:docs/api.html[API Documentation] for
technical details.

=== Architecture Diagram

image::architecture.png[System Architecture, 600]

=== Sample Configuration

[source,yaml]
----
database:
  host: localhost
  port: 5432
  name: myapp_db
----

For questions, contact mailto:[email protected][the team].

Output TEXTILE file (resources.textile):

h2. Resources

Visit our "project website":https://example.com for
more information.

See the "API Documentation":docs/api.html for
technical details.

h3. Architecture Diagram

!architecture.png(System Architecture)!

h3. Sample Configuration

<pre><code>database:
  host: localhost
  port: 5432
  name: myapp_db
</code></pre>

For questions, contact "the team":mailto:[email protected].

Frequently Asked Questions (FAQ)

Q: Will the converted Textile work directly in Redmine?

A: Yes, the converter produces Textile markup that is fully compatible with Redmine's wiki and issue tracking system. You can paste the converted content directly into Redmine wiki pages, issue descriptions, or comments and it will render correctly. Redmine uses Textile as its default markup language.

Q: How are AsciiDoc tables converted to Textile format?

A: AsciiDoc tables are converted to Textile's pipe-based table syntax. Header rows are marked with the _.header notation, and cell content is preserved. Simple tables convert directly; complex merged cells or advanced table features may need manual adjustment for the best appearance.

Q: What happens to AsciiDoc code blocks with syntax highlighting?

A: Code blocks are converted to Textile's pre and code tags. While Textile doesn't have native syntax highlighting, the code content is preserved in a monospace format. Redmine and some Textile processors may add highlighting through plugins or extensions if configured.

Q: Are AsciiDoc admonitions (NOTE, TIP, WARNING) preserved?

A: Admonitions are converted to emphasized text blocks in Textile using bold labels like *Note:* or *Warning:*. While Textile doesn't have native admonition support, the content remains clearly marked and readable. Some platforms may support custom styling for these elements.

Q: How are internal cross-references handled?

A: AsciiDoc cross-references are converted to Textile wiki-style links where possible. For Redmine, you may need to adjust links to match your wiki page structure using [[PageName]] syntax. External URLs are converted to standard Textile link format with "text":url syntax.

Q: Can I convert documents with images and attachments?

A: Image references are converted to Textile's image syntax using !image.png! format. The image files themselves need to be uploaded separately to your Textile platform (e.g., as Redmine attachments). The converter preserves image paths and alt text for reference.

Q: What AsciiDoc features are not supported in Textile?

A: Some advanced AsciiDoc features have limited Textile equivalents: includes, complex nested structures, document attributes, callouts, and conditional content. These are converted to the closest Textile alternative or preserved as plain text. Mathematical notation also requires special handling.

Q: Is the converted Textile compatible with platforms besides Redmine?

A: Yes, the output follows standard Textile syntax and works with Textpattern CMS, various wiki platforms, and any system supporting RedCloth or similar Textile processors. Minor adjustments may be needed for platform-specific extensions or custom formatting requirements.