[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MIT-Scheme-devel] a MIME body structure parser for non-IMAP folders
From: |
Chris Hanson |
Subject: |
Re: [MIT-Scheme-devel] a MIME body structure parser for non-IMAP folders in IMAIL |
Date: |
Tue, 29 Nov 2005 01:06:02 -0500 |
On 11/28/05, Taylor Campbell <address@hidden> wrote:
> Sorry, I meant to add one other thing to the question: would it have
> to be GPL'd as well?
I'd prefer that, and so would the GNU project, but you can use any
GPL-compatible license for your changes.
I just re-read some of the maintainers' documentation
(http://www.gnu.org/prep/maintain/) and I see that it's not necessary
to add a copyright line specifically in your name:
You can also include copyright notices for other copyright holders as well,
and this is a good idea for those who have contributed a large amount
and for those who specifically ask for notices in their names. But you
don't have to include a notice for everyone who contributed to the file,
and that would be rather inconvenient.
So I guess it's up to you what you want to do. We're supposed to have
an AUTHORS file that records who has done what -- although I think the
automatically generated ChangeLog is sufficient.
> OK, thanks. (Is it a bug that string ports disregard line ending
> normalization settings?)
I guess it's a bug. The theory of strings is that they are ISO 8859-1
encodings with normalized line endings. In practice, though, they are
sometimes treated differently (for example as UTF-8 encodings), and
the "theory" is just the default state when you have no additional
knowledge about the string's interpretation. Consequently, it makes
sense for string ports to support translation when a string is used in
a non-default way.
Probably I was thinking only of the theoretical model when I
implemented string ports.
I'll make this change.