This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug localedata/11213] localedata licencing issues
- From: "cjlhomeaddress at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Mon, 16 Jul 2012 18:22:04 +0000
- Subject: [Bug localedata/11213] localedata licencing issues
- Auto-submitted: auto-generated
- References: <bug-11213-131@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 on the CC list for the bug.