-
Notifications
You must be signed in to change notification settings - Fork 1
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
Updates & Licensing #1
Comments
I can confirm that data provided by LSHK is licensed under CC BY 4.0
The iso10646hk.net website is no longer actively maintained. The HKSAR OGCIO website does not contain a license, but it is stated that the list is free of charge, for citizens' reference and use ("免費供市民參考及使用"). |
@chaaklau Thanks! |
Thinking about it more, that's seems like a public domain declaration without actually going so far as to say it. It'd hinge on 市民 (I think I would count as I am a resident) and if those rights are retransmittable. The most-careful approach is to do any downloading transformation of this data on end-user-device so that I'm not distributing possibly-copyrighted work. That works for any install-based setup with long-term storage, but would be prohibitive for web-based usage. I wonder if I can get OGCIO to make a more-clear statement. Email I am sending to them: Hello OGCIO! I'm trying to determine the copyright and license status of the "Cantonese Pronunciation List of the Characters for Computers" document produced for ISO 10646. In Cantonese the site (https://www.ogcio.gov.hk/tc/our_work/business/tech_promotion/ccli/cliac/canton_pronun_list.html) explicitly states, "免費供市民參考及使用。"
It would be excellent to be able to include this data into Unicode's Unihan database and in order to do so there needs to be clarity around the copyright and licensing status of the document and its contents. Thanks for your help!(我識睇中文字) |
Did you receive a response? |
@wtn nope. |
@chaaklau has made edits to the source data which can be seen here.
Should this library optionally apply that diff?
@chaaklau:
The text was updated successfully, but these errors were encountered: