patterns/hyph-sk.tex: licence header is outdated (Slovak patterns are now MIT)

Open Beginner friendly
#36 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
84/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
latex, rust
Domain
documentation

Research direction

The file to change is patterns/hyph-sk.tex; only the % licence: lines at the top need updating, from GPL-2.0-or-later to MIT with the upstream URL. Compare against upstream's version of that header first, then optionally run tests/generate.rs to confirm tries/sk.bin stays byte-identical. Done when the header matches upstream and the generated trie is unchanged.

Written by the indexing model from the issue text.

Description

The copy of hyph-sk.tex in patterns/ still states GPL-2.0-or-later in its % licence: header. Upstream tex-hyphen changed the licence of the Slovak patterns to MIT in commit 645e87e (2026-02-18, "Changed licence of the Slovak patterns to MIT."; CTAN release 2026.02.21: "Updated licence of Slovak patterns to MIT"), and TeX Live 2026 ships that file.

The pattern data is identical — a diff of the two files shows only the % licence: lines (name: GPL / version: 2 / or_later: true / url: … → name: MIT / url: …). Rebuilding the trie from either file with tests/generate.rs gives a byte-identical tries/sk.bin (13,069 bytes), so updating the header from upstream would not change the shipped data, only the licence information downstream users see when they audit the crate.

Dominant language
TeX
Stars
147
Forks
22
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from typst/hypher

All issues in typst/hypher

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.