From: "cjlhomeaddress at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sources.redhat.com
Subject: [Bug localedata/11213] localedata licencing issues
Date: Mon, 16 Jul 2012 18:31:00 -0000 [thread overview]
Message-ID: <bug-11213-716-tgbIP8fVnN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11213-716@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=11213
--- Comment #21 from Chris Leonard <cjlhomeaddress at gmail dot com> 2012-07-16 18:22:04 UTC ---
I think there is something to the analogy that "glibc locale" is to "glibc" as
"PO file" is to "YOUR_PACKAGE_NAME_HERE". Similar purposes are served in both
cases, with specific, properly-formatted information being supplied by the
localizer to allow usage of (in this case glibc) in their language.
The common licensing / copyright header lines in a PO file are:
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR OF THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
This is certainly most localizers expectation of how their work will be
licensed and they will credited, it stands to reason that glibc locale
developers will have similar expectations, but that is merely opinion and not
in any way a legal argument.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-07-16 18:31 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11213-716@http.sourceware.org/bugzilla/>
2012-07-13 18:57 ` jrnieder at gmail dot com
2012-07-14 4:40 ` tg at mirbsd dot de
2012-07-14 4:40 ` cjlhomeaddress at gmail dot com
2012-07-14 4:41 ` jrnieder at gmail dot com
2012-07-14 4:41 ` tg at mirbsd dot de
2012-07-15 15:03 ` tg at mirbsd dot de
2012-07-15 15:03 ` cjlhomeaddress at gmail dot com
2012-07-15 16:06 ` jrnieder at gmail dot com
2012-07-15 21:18 ` tg at mirbsd dot de
2012-07-15 21:18 ` jrnieder at gmail dot com
2012-07-15 21:18 ` pasky at ucw dot cz
2012-07-15 21:18 ` jrnieder at gmail dot com
2012-07-16 0:42 ` Keld Simonsen
2012-07-16 0:45 ` keld at keldix dot com
2012-07-16 1:19 ` jrnieder at gmail dot com
2012-07-16 10:03 ` keld at keldix dot com
2012-07-16 13:44 ` pasky at ucw dot cz
2012-07-16 16:38 ` Keld Simonsen
2012-07-16 13:52 ` tg at mirbsd dot de
2012-07-16 17:04 ` Keld Simonsen
2012-07-16 16:43 ` keld at keldix dot com
2012-07-16 17:04 ` keld at keldix dot com
2012-07-16 18:31 ` cjlhomeaddress at gmail dot com [this message]
2012-07-16 18:50 ` help at softwarefreedom dot org
2012-07-16 18:51 ` help at softwarefreedom dot org
2012-07-16 18:52 ` help at softwarefreedom dot org
2012-07-16 18:53 ` help at softwarefreedom dot org
2012-07-17 15:53 ` jrnieder at gmail dot com
2012-07-25 17:53 ` cjlhomeaddress at gmail dot com
2014-06-30 20:57 ` fweimer at redhat dot com
2016-02-19 10:47 ` [Bug localedata/11213] localedata: add copyright disclaimer to locale files vapier at gentoo dot org
2016-03-21 6:31 ` cvs-commit at gcc dot gnu.org
2016-03-21 6:31 ` vapier at gentoo dot org
2016-08-02 3:28 ` cvs-commit at gcc dot gnu.org
2010-01-23 16:27 [Bug localedata/11213] New: localedata licencing issues tg at mirbsd dot de
2010-04-04 18:31 ` [Bug localedata/11213] " drepper at redhat dot com
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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-11213-716-tgbIP8fVnN@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@sources.redhat.com \
/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).