Bug #12598: List files with Unicode license in LEGAL file

• Status: Closed
• Assignee: duerst (Martin Dürst)
• Target version: -
• Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN

[duerst (Martin Dürst)]

From https://bugs.ruby-lang.org/issues/12529:

enc/trans/*/.src

$ ls enc/trans/**/*.src | xargs grep -i copyright
enc/trans/GB/GB12345%UCS.src:#  Copyright (c) 1991-1994 Unicode, Inc.  All Rights reserved.
...

enc/trans/GB/*.src files are not covered within the file.

It must be Unicode or Unicode Character Database (UCD) license.

This issue is also related on https://bugs.ruby-lang.org/issues/11844 .

[duerst (Martin Dürst)]

• Blocks Misc #12529: LEGAL file covering all the license information within Ruby added

[hsbt (Hiroshi SHIBATA)]

• Assignee changed from duerst (Martin Dürst) to hsbt (Hiroshi SHIBATA)

[hsbt (Hiroshi SHIBATA)]

• Status changed from Open to Closed

Applied in changeset r55724.

---

• LEGAL: Added entries for files under the USD license.
  [Bug #12598][ruby-core:76428][ci skip]

[hsbt (Hiroshi SHIBATA)]

• Status changed from Closed to Assigned
• Assignee changed from hsbt (Hiroshi SHIBATA) to duerst (Martin Dürst)

[hsbt (Hiroshi SHIBATA)]

• Related to Misc #12529: LEGAL file covering all the license information within Ruby added

[hsbt (Hiroshi SHIBATA)]

• Blocks deleted (Misc #12529: LEGAL file covering all the license information within Ruby)

[naruse (Yui NARUSE)]

Though GB2312 seems still needed, but we may be able to remove GB12345.

[hsbt (Hiroshi SHIBATA)]

I discussed UCD license on the Ruby language with Prof. Martin.

enc/trans/GB/.src files have a wrong license holder message about UCD. Example: its message points another dataset.
We will put a disclaimer message into a top of enc/trans/GB/.src files and will remove current UCD license message.

[duerst (Martin Dürst)]

To give some more details on what Hiroshi wrote, what happened (actually upstreams, not at Ruby itself) is that somebody took some of the Unicode data files and used them to produce a product supporting Unicode, as permitted in the copyright for those files.

The resulting files bear some similarity to the original ones, but that similarity is limited to using 0xABCD notation and the "one line per entry" convention (stuff used widely throughout the community), and containing the same mappings (which is explicitly what's needed to "produce a product supporting Unicode"). The number of columns and the order of columns and entries has been changed. Some new headers have been added.

Whoever did this work kept all the explanatory text and the copyright notice, but the explanatory text does no longer apply (it's explicitly wrong). Once that's gone, the copyright notice is also no longer necessary, because the result is not a copy of the original file, but use of the data in the original file which is explicitly permitted.

I'm therefore going to replace these copyright notices with a very short notice explaining the above facts. This short notice will also say that Unicode, Inc. never made any claims as to fitness of that file for any particular purpose, and has ceased to publish the file many years ago. I'm doing that because in discussions with people at the Unicode consortium, it turned out that the main reason they don't want to republish these old files with a new copyright (as they have done for other files) is that they are afraid to give any impression of "correctness" for these files.

[duerst (Martin Dürst)]

• Status changed from Assigned to Closed

Applied in changeset trunk|r59715.

---

replace copyrights by explanatory text in data files for GB2312/GB12345 mappings

Replace the copyrights and explanatory texts in the data files used for mapping
GB2312/GB12345 to/from Unicode with short explanatory texts. [Bug #12598] [ci skip]

[shyouhei (Shyouhei Urabe)]

• Related to Bug #16820: LEGAL is out of sync added