On Sat, 2 Mar 2002 07:05:55 -0500 Glenn Maynard <[EMAIL PROTECTED]> wrote:
> On Sat, Mar 02, 2002 at 01:42:13AM -0500, Michael B Allen wrote: > > Can I statically link of the codepage headers (e.g. cp1252.h) from > > libiconv with an MIT Licensed module? I would not actually alter the > > file of course so a user could not modify the LGPL files in my module > > any more than if they had used libiconv directly. > > The LGPL is designed to allow programs with GPL-incompatible licenses to > link against them; that license (assuming you mean > http://www.jclark.com/xml/copying.txt) is GPL-compatible (says Very strange that you ref. James Clarks site because it is his expat product that encouraged me to license my DOM as MIT and I want to use the libiconv codepage "headers" to add support for extended character sets to this DOM that uses expat. > http://www.gnu.org/licenses/license-list.html), so you could link against > it even if the header in question was GPL'd. (Strictly speaking, using > headers isn't linking; I'm not sure how this is covered in the license, > but the LGPL would be useless if it permitted linking but not including.) Well actually these "headers" are not public and have code in them. The design calls for abstracting the conversion of a character to and from ucs codes by using a function pointer to code included in different many different files. Regardless of the fact that these include files are .h files they each have code in them. > > IANAL nor a license expert; assume all of the above is false. You'd be > much better off looking for a license-oriented list or mailing the FSF. Ok. Thanks, Mike -- May The Source be with you. -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
