| Age | Commit message (Collapse) | Author | Lines |
|
The text of <https://unicode.org/license.txt> was swapped out from
"UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE" to "UNICODE
LICENSE V3" between the dates of 2023.06.03 and 2023.09.11, which means
between Unicode 15.0.0 (2022.09.13) and Unicode 15.1.0 (2023.09.12).
https://web.archive.org/web/20230603182532/https://www.unicode.org/license.txt
https://web.archive.org/web/20230911222703/https://www.unicode.org/license.txt
https://unicode.org/versions/Unicode15.0.0/
https://unicode.org/versions/Unicode15.1.0/
A license wording change is not mentioned in the 15.1.0 release
summary or announcement post.
https://www.unicode.org/versions/Unicode15.1.0/
http://blog.unicode.org/2023/09/announcing-unicode-standard-version-151.html
But I guess we are intended to infer that data files from Unicode 15.1.0
should be specified as licensed Unicode-3.0 as opposed to
Unicode-DFS-2016.
https://spdx.org/licenses/Unicode-3.0.html
https://spdx.org/licenses/Unicode-DFS-2016.html
|
|
|
|
|
|
Also remove to licenses we no longer need, and given REUSE.toml reads some basic idea of what it's about.
|
|
A `reuse --include-submodules lint` now passes.
|
|
|
|
* Adding CC0-1.0 from https://creativecommons.org/publicdomain/zero/1.0/legalcode.txt
* Adding CC-BY-3.0 from https://creativecommons.org/licenses/by/3.0/legalcode.txt
|
|
|
|
|
|
|
|
|
|
This allows it to be used by other codegen backends
|
|
|
|
|
|
|