I am trying to package this project for Fedora¹ and we've encountered ambiguous license issue. The suggestion was that it should be licensed under(MIT OR Apache-2.0) AND Unicode-DFS-2016 due toscripts/unicode.py

There could be another possibility to simply excludescripts/* from crate, but I am not sure if the generated code is under the same license Unicode license or not.

Footnotes

https://bugzilla.redhat.com/show_bug.cgi?id=2279853 ↩

LecrisUT added2 commits

May 11, 2024 07:09

Exclude scripts from crate

3cad478

Add unicode license

a6f9361

Copy link

ContributorAuthor

LecrisUT commentedMay 11, 2024

I was also pointed tothis discussion which seems to suggest that the generated files would have to have theUnicode-DFS-2016 license attached iiuc.

Copy link

musicinmybrain commentedMay 11, 2024

It istables.rs that I believe may actually be (additionally) subject to the license of the Unicode Character Database from which it is derived. The Python script – itcould be excluded from the crate simply because it’s not used by cargo, but I don’t see a reason why itneeds to be.

Copy link

decathorpe commentedMay 13, 2024

As far as I can tell, the situation here is very similar to the unicode-ident crate:https://crates.io/crates/unicode-ident

See alsodtolnay/unicode-ident#9 whereAND Unicode-DFS-2016 was added topackage.license in Cargo.toml.

See alsohttps://github.com/unicode-rs/unicode-xid/pull/32/files for a similar request for a different unicode-rs crate.

musicinmybrain mentioned this pull request

Nov 2, 2025

Add Unicode-3.0 license for Unicode dataunicode-rs/unicode-normalization#116

Merged

Copy link

musicinmybrain commentedNov 2, 2025

It was pointed outdownstream that the license text here isUnicode-3.0, notUnicode-DFS-2016, and thatUnicode-3.0 should indeed be the correct license for Unicode version 17 data.