On Mon, 13 Feb 2006 14:01:24 +0100 (CET) Vincent Torri
<[EMAIL PROTECTED]> babbled:
>
> hello,
>
> for those who do not know, poppler is a library that can parse and render
> pdf content to some kind of 'bitmaps'. I've written an evas frontend for
> it. But the developpers don't want to include
Algorithms are murky territory for copyright. If it could be shown that you have copied their code and just substituted variable/function names, then you would need to follow the GPL, but if it's just using the idea and completely reimplemented, theres no concern. It really just comes down to what
On Mon, 13 Feb 2006, Nathan Ingersoll wrote:
> I have no objections myself. The licensing is a little bit odd in my
> understanding. You could license your sourcecode as BSD, like most of E, as
> long as you don't copy code directly from poppler,
there's a function that I have not copy the code
I have no objections myself. The licensing is a little bit odd in my understanding. You could license your sourcecode as BSD, like most of E, as long as you don't copy code directly from poppler, but if you link against poppler then the executable will be GPL. So you end up with a situation where,
hello,
for those who do not know, poppler is a library that can parse and render
pdf content to some kind of 'bitmaps'. I've written an evas frontend for
it. But the developpers don't want to include it in the poppler cvs until
"a couple of applications start using it". I don't know how people wi
