[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kopete-devel
Subject:    Re: [kopete-devel] Ink draw support in WLM
From:       "Roman Jarosz" <kedgedev () gmail ! com>
Date:       2009-05-11 15:53:15
Message-ID: op.utrvq0m7asvm2a () kedge
[Download RAW message or body]

Hi,

IMHO you can use giflib because all patents has expired already.

This is from Ubuntu package log:
This is giflib 4.x, replacing giflib 3.x. No package in the archive has to
be transitioned. After etch, giflib will replace libungif (all alleged  
patents
are expired all over the world).

And on giflib side there's:
giflib is a library for reading and writing gif images. It is API and ABI
compatible with libungif which was in wide use while the LZW compression
algorithm was patented.

Regards,
Roman

On Mon, 11 May 2009 16:55:41 +0200, Tiago Salem Herrmann  
<salem@mandriva.com> wrote:

> Hi all,
>
> I am working on Ink draw support in WLM but I'm facing some problems, so
> I would like to ask for some opinions.
>
> The two options are to send the image in GIF or ISF
> (http://en.wikipedia.org/wiki/Ink_Serialized_Format).
> Even though ISF is now an open format, libmsn was not tested to send it
> in ISF, and probably writing a code to encode a image to ISF is a waste
> of time, since only a few people will use it and all the MSN clients
> (official and 3dy party) accept GIF.
>
> The problem is that Qt doesn't support writing GIF's, only reading. (as
> far as I understand due to legal issues).
>
> Is it possible to link WLM protocol to libgif?
> Today I'll perform some tests with libungif, but I'm not sure if the
> official client will accept uncompressed gifs.
>
> Does anyone have another/better idea?
>
> Thank you.
>
> Tiago Salem Herrmann
> _______________________________________________
> kopete-devel mailing list
> kopete-devel@kde.org
> https://mail.kde.org/mailman/listinfo/kopete-devel


_______________________________________________
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel
[prev in list] [next in list] [prev in thread] [next in thread]