opentypejs/opentype.js

Corrupted font file handling

Open

#337 opened on Mar 16, 2018

View on GitHub
 (4 comments) (0 reactions) (1 assignee)JavaScript (512 forks)batch import
enhancementhelp wantedquestion

Repository metrics

Stars
 (4,170 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

The more different tables we parse in opentype.js, the more we come across corrupted font files. Most of them are still usable with other software, but opentype.js currently throws errors and stops parsing the font. Shouldn't we try to skip (sub)tables containing errors ? Should we report errors in some way ? Maybe just keeping a log of ignored tables ? What do you think ? @fdb @Jolg42 @Pomax and others ?

Contributor guide

Research direction
Identify which font tables commonly cause errors and implement fallback or logging for corrupted data.
Tech stack
javascript
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaScriptOpenType spec
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40