Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/unicode-org/text-rendering-tests
Unicode’s test suite for text rendering engines
https://github.com/unicode-org/text-rendering-tests
coretext fonts freetype opentype unicode
Last synced: about 2 months ago
JSON representation
Unicode’s test suite for text rendering engines
- Host: GitHub
- URL: https://github.com/unicode-org/text-rendering-tests
- Owner: unicode-org
- License: other
- Created: 2016-09-26T07:16:07.000Z (almost 8 years ago)
- Default Branch: main
- Last Pushed: 2024-03-18T18:04:44.000Z (6 months ago)
- Last Synced: 2024-07-09T03:51:58.923Z (2 months ago)
- Topics: coretext, fonts, freetype, opentype, unicode
- Language: HTML
- Homepage:
- Size: 7.22 MB
- Stars: 164
- Watchers: 32
- Forks: 37
- Open Issues: 17
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-typography - Text rendering tests - Test suite for text rendering. (C++)
README
# Text rendering tests
This is a test suite for text rendering engines. It is not easy to correctly
display text, so we founded this project to help implementations to
get this right.
```bash
$ brew install cmake ninja npm rust
$ git clone --recursive https://github.com/unicode-org/text-rendering-tests.git
$ cd text-rendering-tests
$ for engine in CoreText FreeStack TehreerStack fontkit OpenType.js Allsorts ; do python3 check.py --engine=$engine --output=reports/$engine.html ; done
```
## Supported Platforms
Currently, the test suite supports six OpenType implementations:
* With `--engine=FreeStack`, the tests are run on the free/libre
open-source text rendering stack with [FreeType](https://www.freetype.org/),
[HarfBuzz](https://www.freedesktop.org/wiki/Software/HarfBuzz/),
[FriBidi](https://www.fribidi.org/),
and [Raqm](https://github.com/HOST-Oman/libraqm). These libraries
are used by Linux, Android, ChromeOS, and many other systems.
— [Test report for FreeStack](https://rawgit.com/unicode-org/text-rendering-tests/master/reports/FreeStack.html).
* With `--engine=CoreText`, the tests are run on Apple’s CoreText.
This option will work only if you run the test suite on MacOS X.
— [Test report for CoreText](https://rawgit.com/unicode-org/text-rendering-tests/master/reports/CoreText.html).
* With `--engine=TehreerStack`, the tests are run on an open-source
text rendering stack consisting of [FreeType](https://www.freetype.org/),
[SheenBidi](https://github.com/Tehreer/SheenBidi), and
[SheenFigure](https://github.com/Tehreer/SheenFigure).
— [Test report for TehreerStack](https://rawgit.com/unicode-org/text-rendering-tests/master/reports/TehreerStack.html).
* With `--engine=fontkit`, the tests are run on
[fontkit](http://github.com/devongovett/fontkit), a JavaScript font engine.
— [Test report for fontkit](https://rawgit.com/unicode-org/text-rendering-tests/master/reports/fontkit.html).
* With `--engine=OpenType.js`, the tests are run using [OpenType.js](https://github.com/nodebox/opentype.js), another JavaScript font engine.
— [Test report for OpenType.js](https://rawgit.com/unicode-org/text-rendering-tests/master/reports/OpenType.js.html).
* With `--engine=Allsorts`, the tests are run using [Allsorts](https://github.com/yeslogic/allsorts),
a parsing and shaping engine implemented in [Rust](https://www.rust-lang.org/).
— [Test report for Allsorts](https://rawgit.com/unicode-org/text-rendering-tests/master/reports/Allsorts.html).
It’s trivial to test other implementations; simply write a small
wrapper tool. For the [Go font
library](https://godoc.org/golang.org/x/image/font/sfnt), see
[here](https://github.com/golang/go/issues/20208). For the [Rust font
library](https://github.com/google/font-rs), see
[here](https://github.com/google/font-rs/issues/17).
## Test Cases
The test cases are defined in the [testcases](testcases/) directory.
It contains HTML snippets which describe each test, and define the
rendering parameters together with the expected result.
For each test case, the `check.py` script parses the HTML snippet to
extract the rendering parameters. Then, it runs a sub-process (written
in C++, Objective C, Rust or JavaScript depending on the tested
implementation) that writes the observed rendering in SVG format to
Standard Output. Finally, the script checks whether the expected
rendering matches the observed result. Currently, “matching” is
implemented by iterating over SVG paths, allowing for maximally 1 font
design unit of difference.
### Copyright & Licenses
Copyright © 2016-2024 Unicode, Inc. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. in the United States and other countries.
The project is released under [LICENSE](./LICENSE).
A CLA is required to contribute to this project - please refer to the [CONTRIBUTING.md](https://github.com/unicode-org/.github/blob/main/.github/CONTRIBUTING.md) file (or start a Pull Request) for more information.