From: duerst@it.aoyama.ac.jp
To: ruby-core@ruby-lang.org
Subject: [ruby-core:82645] [Ruby trunk Bug#11844] Please update unicode-licensed files (license issue)
Date: Tue, 05 Sep 2017 07:28:58 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-66477.20170905072856.d334242d1253b242@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11844.20151219124111@ruby-lang.org
Issue #11844 has been updated by duerst (Martin Dürst).
zeha (Christian Hofstaedtler) wrote:
> The non-free problem is with this line: "supplied in this file in the creation of products supporting the Unicode Standard" - which implies that you can't use this file to produce stuff not supporting / not complying with "the Unicode Standard" (which itself may change at any time). (This is a problem for redistributors that may opt to use the GPL for Ruby and also causes DFSG issues.)
Just for the record, with r59715 it still says "supporting Unicode", but our understanding is that we used the original files to create a product (Ruby) supporting the Unicode standard, but the new files that were created are no longer under Unicode copyright, meaning that downstream third-party users should also be fine.
----------------------------------------
Bug #11844: Please update unicode-licensed files (license issue)
https://bugs.ruby-lang.org/issues/11844#change-66477
* Author: zeha (Christian Hofstaedtler)
* Status: Closed
* Priority: Normal
* Assignee: naruse (Yui NARUSE)
* Target version:
* ruby -v: 2.2.3
* Backport: 2.1: DONE, 2.2: DONE, 2.3: DONE
----------------------------------------
Various files in enc/trans are old copies of Unicode.org files that forbid (re-)distribution. AFAICT, Unicode, Inc. has published newer versions of these files to fix this issue.
New versions could possibly be found on http://www.unicode.org/Public/MAPPINGS/OBSOLETE/EASTASIA/JIS/ and elsewhere under http://www.unicode.org/Public/
ext/json/generator/generator.c also has a restrictive Unicode, Inc. license blurb. Please fix this as well.
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2017-09-05 7:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-11844.20151219124111@ruby-lang.org>
2015-12-19 12:41 ` [ruby-core:72379] [Ruby trunk - Bug #11844] [Open] Please update unicode-licensed files (license issue) ch---bugs-ruby-lang
2015-12-20 2:20 ` [ruby-core:72399] [Ruby trunk - Bug #11844] " duerst
2015-12-20 2:21 ` [ruby-core:72400] " duerst
2015-12-20 2:51 ` [ruby-core:72402] " akr
2015-12-20 3:15 ` [ruby-core:72403] [Ruby trunk - Bug #11844] [Feedback] " duerst
2016-03-03 20:02 ` [ruby-core:74114] [Ruby trunk Bug#11844] " ch---bugs-ruby-lang
2016-03-03 20:03 ` [ruby-core:74115] " ch---bugs-ruby-lang
2016-03-16 7:39 ` [ruby-core:74366] " duerst
2016-03-17 0:44 ` [ruby-core:74389] " zeha
2016-03-17 0:53 ` [ruby-core:74390] " shibata.hiroshi
2016-03-24 7:46 ` [ruby-core:74519] " usa
2016-03-25 9:40 ` [ruby-core:74567] " usa
2016-03-28 16:26 ` [ruby-core:74635] " nagachika00
2016-03-29 7:45 ` [ruby-core:74674] " naruse
2016-06-21 15:56 ` [ruby-core:76099] " jaruga
2016-06-28 12:06 ` [ruby-core:76173] " jaruga
2016-06-28 13:39 ` [ruby-core:76177] " jaruga
2017-09-05 7:28 ` duerst [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-66477.20170905072856.d334242d1253b242@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).