A Crystal reimplementation of the Pygments/Chroma syntax highlighters
Go to file
Roberto Alsina d26393d8c9
Some checks are pending
Tests / build (push) Waiting to run
chore: fix example code in README
2024-09-19 11:20:08 -03:00
.github/workflows test: Add CI workflows 2024-09-04 11:39:14 -03:00
lexers feat: use the native crystal highlighter 2024-09-09 16:14:35 -03:00
scripts chore: pre-commit hooks 2024-08-26 20:18:28 -03:00
spec test: added tests for CSS generation 2024-09-10 22:38:04 -03:00
src test: added tests for CSS generation 2024-09-10 22:38:04 -03:00
styles chore: pre-commit hooks 2024-08-26 20:18:28 -03:00
.ameba.yml test: add basic tests for crystal and delegating lexers 2024-09-10 21:57:05 -03:00
.editorconfig Initial dumb stuff 2024-08-02 17:03:39 -03:00
.gitignore chore: updated pre-commit 2024-09-04 11:37:04 -03:00
.md.rb build: fix markdown check 2024-09-04 11:37:36 -03:00
.mdlrc build: fix markdown check 2024-09-04 11:37:36 -03:00
.pre-commit-config.yaml chore: force conventional commit messages 2024-08-26 21:27:38 -03:00
build_static.sh build: fix markdown check 2024-09-04 11:37:36 -03:00
CHANGELOG.md bump: Release v0.7.0 2024-09-18 10:58:15 -03:00
cliff.toml chore(ignore): skip chore+ignore commits in changelog 2024-09-18 10:58:15 -03:00
do_release.sh build: added do_release script 2024-09-04 11:37:36 -03:00
Dockerfile.static Added helper files 2024-08-09 10:32:15 -03:00
Hacefile.yml fix: make install work 2024-09-09 16:16:33 -03:00
LICENSE Initial dumb stuff 2024-08-02 17:03:39 -03:00
README.md chore: fix example code in README 2024-09-19 11:20:08 -03:00
shard.yml bump: Release v0.7.0 2024-09-18 10:58:15 -03:00
TODO.md Load lexer by mimetype 2024-08-24 22:20:38 -03:00

TARTRAZINE

Tests codecov

Tartrazine is a library to syntax-highlight code. It is a port of Pygments to Crystal.

It also provides a CLI tool which can be used to highlight many things in many styles.

Currently Tartrazine supports 247 languages and has 331 themes (63 from Chroma, the rest are base16 themes via Sixteen

Installation

If you are using Arch: Use yay or your favourite AUR helper, package name is tartrazine.

From prebuilt binaries:

Each release provides statically-linked binaries that should work on any Linux. Get them from the releases page and put them in your PATH.

To build from source:

  1. Clone this repo
  2. Run make to build the tartrazine binary
  3. Copy the binary somewhere in your PATH.

Usage as a CLI tool

Show a syntax highlighted version of a C source file in your terminal:

tartrazine whatever.c -l c -t catppuccin-macchiato --line-numbers -f terminal

Generate a standalone HTML file from a C source file with the syntax highlighted:

$ tartrazine whatever.c -t catppuccin-macchiato --line-numbers \
  --standalone -f html -o whatever.html

Usage as a Library

Add to your shard.yml:

dependencies:
  tartrazine:
    github: ralsina/tartrazine

This is the high level API:

require "tartrazine"

html = Tartrazine.to_html(
  "puts \"Hello, world!\"",
  language: "crystal",
  theme: "catppuccin-macchiato",
  standalone: true,
  line_numbers: true
)

This does more or less the same thing, but more manually:

lexer = Tartrazine.lexer("crystal")
formatter = Tartrazine::Html.new(
  theme: Tartrazine.theme("catppuccin-macchiato"),
  line_numbers: true,
  standalone: true,
)
puts formatter.format("puts \"Hello, world!\"", lexer)

The reason you may want to use the manual version is to reuse the lexer and formatter objects for performance reasons.

Contributing

  1. Fork it (https://github.com/ralsina/tartrazine/fork)
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request

Contributors

A port of what, and why "kind of"

Pygments is a staple of the Python ecosystem, and it's great. It lets you highlight code in many languages, and it has many themes. Chroma is "Pygments for Go", it's actually a port of Pygments to Go, and it's great too.

I wanted that in Crystal, so I started this project. But I did not read much of the Pygments code. Or much of Chroma's.

Chroma has taken most of the Pygments lexers and turned them into XML descriptions. What I did was take those XML files from Chroma and a pile of test cases from Pygments, and I slapped them together until the tests passed and my code produced the same output as Chroma. Think of it as extreme TDD

Currently the pass rate for tests in the supported languages is 96.8%, which is not bad for a couple days hacking.

This only covers the RegexLexers, which are the most common ones, but it means the supported languages are a subset of Chroma's, which is a subset of Pygments' and DelegatingLexers (useful for things like template languages)

Then performance was bad, so I hacked and hacked and made it significantly faster than chroma which is fun.