[cairo] rendering UTF8 text
Ulrich Mierendorff
ulrich.mierendorff at gmx.net
Tue Jun 26 02:35:48 PDT 2007
Hi,
Sorry, I did not mean cairo depends on glib but pango depends on it. But
if gettext is LGPL it should not be a problem.
But I do not know if (windows) users/developers like to build/download
dozens of libraries just to use my library. The whole glib etc. things
make that overcomplicated and I just wanted to render some text ;-)
Regards,
Ulrich Mierendorff
Tor Lillqvist schrieb:
> Ulrich Mierendorff writes:
> > But it is true that it depends on glib
>
> cairo does not depend on glib. What makes you think that?
>
> > which depends on gettext which is GPLed. And the GPL is a problem
> > for me and others.
>
> gettext is not wholly GPL. The file gettext-runtime/COPYING from
> gettext 0.16.1 says:
>
> [[
> The gettext-runtime package is partially under the LGPL and
> partially under the GPL.
>
> The following parts are under the LGPL, see files
> intl/COPYING.LIB-2.0 and intl/COPYING.LIB-2.1:
> - the libintl and libasprintf libraries and their header files,
> - the libintl.jar Java library,
> - the GNU.Gettext.dll C# library,
> - the gettext.sh shells script function library.
>
> The following parts are under the GPL, see file COPYING in the
> toplevel directory:
> - the _programs_ gettext, ngettext, envsubst,
> - the documentation.
> ]]
>
> In gettext 0.14.5, the file was even shorter:
>
> [[
> The gettext-runtime package is under the LGPL, see files
> intl/COPYING.LIB-2.0 and intl/COPYING.LIB-2.1.
> ]]
>
> So the gettext runtime library "libintl", which is what matters at
> runtime for applications, is definitely LGPL.
>
> --tml
>
>
--
ulrich.mierendorff at gmx.net
More information about the cairo
mailing list