Comparison

Nano Markup vs TOML.

TOML is a popular configuration format with typed scalar values and table syntax. Nano Markup is smaller: a tree of strings, mappings, and sequences written with indentation.

At a glance

Tables and types, or a small tree

StructureNano Markup nests data by indentation. TOML uses keys, tables, arrays, and arrays of tables.

TypesNano Markup stores scalar text as strings. TOML supports numbers, booleans, dates, times, arrays, and inline tables.

Multiline textNano Markup uses block strings with |. TOML uses multiline string delimiters.

Best fitNano Markup fits simple document-shaped data. TOML fits application configuration that benefits from typed values.

Same data

A profile in both formats

Nano Markup

..
    name Ariana
    active true
    address..
        city Bratislava
        country Slovakia

TOML

name = "Ariana"
active = true

[address]
city = "Bratislava"
country = "Slovakia"

Nano Markup keeps every scalar as text, while TOML interprets true as a boolean and uses a table header for nested data. The right choice depends on whether a small string-based tree or typed configuration is more useful to your application.

Choosing

Use the format that matches the job

Choose Nano Markup if a strict, readable tree is the main goal and your application already knows how to interpret strings. Choose TOML if native typed values and mature configuration tooling are more important.

Both formats are useful. Nano Markup is intentionally narrower, which can be an advantage when implementations must stay small and interoperable.

See the comparisons with YAML and JSON, then browse the examples.