|
||
---|---|---|
.github/workflows | ||
fonts | ||
lexers | ||
scripts | ||
spec | ||
src | ||
styles | ||
.ameba.yml | ||
.editorconfig | ||
.gitignore | ||
.md.rb | ||
.mdlrc | ||
.pre-commit-config.yaml | ||
build_static.sh | ||
CHANGELOG.md | ||
cliff.toml | ||
do_release.sh | ||
Dockerfile.static | ||
Hacefile.yml | ||
LICENSE | ||
README.md | ||
shard.yml | ||
TODO.md |
TARTRAZINE
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:
- Clone this repo
- Run
make
to build thetartrazine
binary - 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
- Fork it (https://github.com/ralsina/tartrazine/fork)
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git commit -am 'Add some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create a new Pull Request
Contributors
- Roberto Alsina - creator and maintainer
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.