--===============1834613793==
Content-Type: multipart/signed;
  boundary="nextPart1389448.VXBzXtSuKr";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1389448.VXBzXtSuKr
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Sunday 11 June 2006 15:06, Jaison Lee wrote:
> > It should be (c). I don't remember what we concluded in another mailing
> > list about the forced use of non-ASCII characters in every file.
>
> Well, it does not *have* to be (c). At least not for US copyright:
> http://www.copyright.gov/circs/circ03.html

KDE is not a US entity, and there are other jurisdictions to care about. =20
However, nearly all of them are signatories to the Berne Convention.

> The word "Copyright" is legally acceptable, and shows up correctly in
> every locale. :)
>
> The only thread I was able to find was this one:
> http://lists.kde.org/?t=3D112224483400002&r=3D1&w=3D2
> but I'm not taking that as canon because the advice there is to use
> (C) and that is not a legally useful symbol. You yourself pointed out
> that all files are in UTF-8, and I would add that we have many, many
> contributors that have names that require non-ASCII characters. Even
> so, since (c) is not necessary, I don't see the point of forcing a
> change just to be pretty.

I stand by what I said in that thread

http://lists.kde.org/?l=3Dkde-core-devel&m=3D114185818326668&w=3D2

> Right now, the best policy would be to:
>
> 1) Require the word 'Copyright'.
> 2) Accept but do not force the use of (c).

> 3) Eliminate all occurrances of (C) on the grounds that it is misleading.

C, in either lower or upper case, in or outside a pair of braces, does not=
=20
provide any protection, and is not just misleading, it is meaningless. you=
=20
may as well allow 7y3 as a copyright symbol, because it will have as much=20
effect. This pointless pseudo-notation should be firmly and clearly outlawe=
d,=20
in my opinion.

> Does something like this need to be okayed by KDE e.V.? How formal is
> the submission process?

There is, btw, a very well researched, approved by a legal type person, if=
=20
perhaps a little out of date, set of trademark acknowledgements in the KDE=
=20
documentation.  If you can wait a few hours, I will send you a copy.

=2D-=20
Lauri Watts

--nextPart1389448.VXBzXtSuKr
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (FreeBSD)

iD8DBQBEldW0/gUyA7PWnacRAmZEAJ9kexLCy1NQuz1Waqs5ak0uf7FgggCdEr0Y
g7NPotz5NcS4lpuootxkJ3w=
=FBcj
-----END PGP SIGNATURE-----

--nextPart1389448.VXBzXtSuKr--

--===============1834613793==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-policies mailing list
Kde-policies@kde.org
https://mail.kde.org/mailman/listinfo/kde-policies

--===============1834613793==--