public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "keld at keldix dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sources.redhat.com
Subject: [Bug localedata/11213] localedata licencing issues
Date: Mon, 16 Jul 2012 17:04:00 -0000	[thread overview]
Message-ID: <bug-11213-716-9akjS2lpc3@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 #20 from keld at keldix dot com <keld at keldix dot com> 2012-07-16 17:04:02 UTC ---
On Mon, Jul 16, 2012 at 01:13:31PM +0000, tg at mirbsd dot de wrote:
> http://sourceware.org/bugzilla/show_bug.cgi?id=11213
> 
> --- Comment #18 from Thorsten Glaser <tg at mirbsd dot de> 2012-07-16 13:13:31 UTC ---
> Keld, while you may have had a lot of ???sweat of brow???, in the end, the locale
> data (in the one file I looked at) is mere fact, and there is, basically, only
> one way to express such facts using the format glibc expects.

Yes, some of the locales are stright forward. But if you look at the whole
combination of a locale, with the LC_COLLATE, the LC_CTYPE, and the
transliteration
specs, there is not only sweat in it but a lot of decisions.
Even the LC_MESSAGES data for yes and no contains a number of variations to
consider.
And even the LC_TIME has some tricks. The choices is a common subject we talk
about on the
localedata reflector, because there are different ways of doing a lot of
things in the locale data. And when there is choice, there is creativity
and work height.

> This is, at
> least, under the EU interoperability directive, not copyrightable (neither are
> *.h files, unless they include insane amounts of inline functions, by the way).
> As for the USA, you probably know that better than I do, but the work, while it
> may have cost you a lot of creativity, is mostly ???sweat of brow???, to express
> the fact that way. You may have designed the interface, the character naming
> convention, etc. but these are interfaces, not works in the sense of copyright.
> I really do not want you to lose any attribution of that, but I don???t believe
> the (one file I looked at with) locale information as shown is not
> copyrightable.

(maybe too many negations here - but I think I know what you mean.)
I think there is differences of what level of work height that is needed for it
to be 
copyrightable in different countries. but I would be astonished if say 1000
lines of
data with a number of serious design decisions on the solutions did not
enjoy copyright in any country (under the Berne convention)..


I do think locales per se are works. They are freestanding items, that are
supposed then to
work toghether with other parts to make a functioning system.

> ???something that could have been patentetd???[sic] is of different scope than
> copyright relevant work. I also fear you could probably have patented it, but
> not put it under copyright protection. (Jonathan, mere effort is also not
> enough in Germany, although USA???s ???sweat of brow??? doctrine is a tad stronger.
> Still, we???re facing interoperability interfaces here, and mere fact; the
> currency of the USA is the Dollar, no matter what.)

:-)

best regards
keld

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2012-07-16 17:04 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 ` cjlhomeaddress at gmail dot com
2012-07-14  4:40 ` tg at mirbsd dot de
2012-07-14  4:41 ` tg at mirbsd dot de
2012-07-14  4:41 ` jrnieder at gmail dot com
2012-07-15 15:03 ` cjlhomeaddress at gmail dot com
2012-07-15 15:03 ` tg at mirbsd dot de
2012-07-15 16:06 ` jrnieder at gmail dot com
2012-07-15 21:18 ` jrnieder at gmail dot com
2012-07-16  0:42   ` Keld Simonsen
2012-07-15 21:18 ` pasky at ucw dot cz
2012-07-15 21:18 ` jrnieder at gmail dot com
2012-07-15 21:18 ` tg at mirbsd dot de
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 [this message]
2012-07-16 18:31 ` cjlhomeaddress at gmail dot com
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 ` vapier at gentoo dot org
2016-03-21  6:31 ` cvs-commit at gcc dot gnu.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-9akjS2lpc3@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).