Missing COPYING in source

[nucleo]

Is it possible to add COPYING to source code?
It is necessary to packaging.

[Jussi Pakkanen (jpakkane)]

What do you mean? What is COPYING exactly and where does it need to be added?

[deleted (to-delete)]

On Wednesday 29 April 2009 23:42:28 JussiP wrote:
> What do you mean? What is COPYING exactly and where does it need to be
> added?
COPYING is the file with the copyright text of the project (BSD-3 text in your
case). Distributions have sometimes strict restriction what files must be
copied when you install the package. Debian allows to write a own copyright
file with the copyright texts/link to it and the authors. Maybe one of the rpm
based distribution doesnt use/allows that.

Look for example at coreutils to see what it looks like for GPL and dotgnu for
LGPL (which needs the COPYING of GPL too and thereof uses COPYING.lesser for
the actual copyright text). See libvorbis as an example how it should look for
BSD-3.
--
Robert Wohlrab

[nucleo (nucleo)]

Now I found license files in
/cuneiform_src/Kern/license.txt, the same file /cuneiform_src/Addfiles/license.txt
and /cuneiform_src/Kern/icrashreport/sources/crashrpt/src/license.txt.
At first I have not found these files. Sorry fo that.
It is necessary for packaging in Fedora to include a copy of the full texts of the licenses in distribution archive.

[Jussi Pakkanen (jpakkane)]

Is cuneiform_src/Addfiles/license.txt sufficient for you to create COPYING? Do we actually need to add/rename anything?

[nucleo (nucleo)]

May be it is sufficient to include in RPM file cuneiform_src/Addfiles/license.txt and no need to rename anything but may be it is make sense to convert license.txt and readme.txt to UTF-8 (not utf-8 file causes rpmlint error).
Is it necessary to include in RPM file cuneiform_src/Kern/icrashreport/sources/crashrpt/src/license.txt ?

[nucleo (nucleo)]

What license should be used for RPM package with cuneiform datafiles ?

[Jussi Pakkanen (jpakkane)]

They are BSD too AFAICT.

The problem with UTF-8 is that Windows does not understand it and we want to support that as well.

[Yury V. Zaytsev (zyv)]

On Tue, 2009-05-05 at 10:58 +0000, JussiP wrote:
>
> The problem with UTF-8 is that Windows does not understand it and we
> want to support that as well.

Why do you think that Windows does not understand UTF-8? Every NT-based
system contains multibyte API. Just try to open some UTF-8 encoded files
in Notepad and you will see that it works fine.

The point is that *by default* it normally uses single-byte encoding
(which one exactly depends on the current locale, e.g. Russian versions
of Windows use Windows-1251, European use Windows-1250 etc.). But this
is subject to change, I think that Notepad would use UTF-8 by default
starting from Windows 7.

I remember they even had a so-called "Unicode update" for those who are
still using 9x/ME.

--
Sincerely yours,
Yury V. Zaytsev

[Jussi Pakkanen (jpakkane)]

The problem with Windows in general is that even though it can be made to do lots of things, "by default" it does the wrong thing. Just like now. Unfortunately we can't rely on all (or even most) interested developers to be running Windows 7.

[nucleo (nucleo)]

Is there source code for datafiles?
How datafiles can be produced?

[Yury V. Zaytsev (zyv)]

On Tue, 2009-05-05 at 18:33 +0000, JussiP wrote:
> The problem with Windows in general is that even though it can be made
> to do lots of things, "by default" it does the wrong thing.

That's exactly why I avoid using it by all means.

> Just like now. Unfortunately we can't rely on all (or even most)
> interested developers to be running Windows 7.

I don't get your point.

Are you afraid that readme.txt will become unreadable under Windows if
you transcode it to UTF-8? It won't, because Notepad, Write, Word etc.
already DO support UTF-8 even in 2K/XP/Vista, they just don't SAVE the
files in UTF-8 *by default*.

Are you afraid that the source code itself will become unreadable? As I
said, Notepad supports it, as well as most of the advanced code editors
and IDEs (e.g. Komodo which I heavily use does support it).

If you want, I can check whether Visual Studio will be able to open and
compile UTF-8 encoded C++ source code, but I bet it will.

--
Sincerely yours,
Yury V. Zaytsev

[Jussi Pakkanen (jpakkane)]

I tried this and it actually works. Color me impressed. I would have expected it to use the windows codepage or something other (since every valid UTF-8 character sequence is also a valid win codepage one).

I have attached a test file in case someone else wants to try this.

[Jussi Pakkanen (jpakkane)]

The original issue has been fixed and license and readme are now UTF-8, so closing.

The discussion on converting to UTF-8 has been moved to the mailing list.