-
Notifications
You must be signed in to change notification settings - Fork 450
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add unicode license for the unicode tables in regex-syntax #530
Comments
In principle this sounds fine to me. But I don't actually know what the requirements are here though. What, specifically, is needed? Reading your link, I don't think I see any requirement to link to those terms of use? Moreover, it's not clear to me whether data derived from Unicode's tables falls under those terms of use. |
We need the license terms around that data to be clear, and the unicode terms of use state that their data can be modified and distributed only if their copyright and permission notice appears with "all copies (I'm assuming derived == modified here, I'm not a lawyer though) |
I guess the root of this is the question "did the data in this directory come from the unicode consortium"? If not, great. If it did, we'd love it if you could include that license. I can make a pull request to add it if that helps. |
It did. A PR would be welcome. |
Add the Unicode license to the unicode-tables directory, as the data there comes from the Unicode Consortium. Fixes rust-lang#530
Add the Unicode license to the unicode-tables directory, as the data there comes from the Unicode Consortium. Fixes rust-lang#530
Add the Unicode license to the unicode-tables directory, as the data there comes from the Unicode Consortium. Fixes rust-lang#530
Add the Unicode license to the unicode-tables directory, as the data there comes from the Unicode Consortium. Fixes #530
We noticed that regex-syntax uses tables derived from unicode 11, but the license files don't include a reference to the unicode terms of use. Could this be added? Thanks so much!
The text was updated successfully, but these errors were encountered: