Hi Mattia,
Thanks for pointing out that very important issue. I fear we have to remove
this code before the release, which would require a second release
candidate and will delay the release currently planned for February 2nd.
The best option seems to be to replace our current implementation with this
BSD licensed code:
http://www.bsdua.org/files/unicode.tar.gz (Linked from
http://unicode.org/resources/utf8.html)
Another option would be to replace it with the original file without
modifications (as done in Ghostscript or taglib):
https://ghostscript.com/doc/base/ConvertUTF.c
http://developer.kde.org/~wheeler/files/src/taglib-0.95/
taglib/toolkit/unicode.cpp
I will have to take a deeper look into this issue!
Best regards,
Dominik
On Wed, Jan 25, 2017 at 3:08 PM, Mattia Rizzolo <mat...@mapreri.org> wrote:
> It seems there is a excerpt of code in src/base/PdfString.cpp coming
> from Unicode, Inc.
> The license of that code is as follow:
>
> /*
> * Copyright 2001-2004 Unicode, Inc.
> *
> * Disclaimer
> *
> * This source code is provided as is by Unicode, Inc. No claims are
> * made as to fitness for any particular purpose. No warranties of any
> * kind are expressed or implied. The recipient agrees to determine
> * applicability of information provided. If this file has been
> * purchased on magnetic or optical media from Unicode, Inc., the
> * sole remedy for any claim will be exchange of defective media
> * within 90 days of receipt.
> *
> * Limitations on Rights to Redistribute This Code
> *
> * Unicode, Inc. hereby grants the right to freely use the information
> * supplied in this file in the creation of products supporting the
> * Unicode Standard, and to make copies of this file in any form
> * for internal or external distribution as long as this notice
> * remains attached.
> */
>
> Such license is not free, as:
> 1) it doesn't grant right to modify the code (which you did, so
> technically you'd be in violation)
> 2) it is worded in a way that seems to limit the usage of the code,
> only in works aimed at supporting the Unicode standard.
>
> Now, apparently Unicode, Inc changed its standard licenses few years
> ago, and so if there is a new version of that code it might be possible
> to pull that and have a really free license (I don't know how feasible
> it is, according to your local changes).
> Another way would be of course to reimplement those functions. Or to
> depend on similar implementations coming from external libraries.
>
> --
> regards,
> Mattia Rizzolo
>
> GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
> more about me: https://mapreri.org : :' :
> Launchpad user: https://launchpad.net/~mapreri `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Podofo-users mailing list
> Podofo-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/podofo-users
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Podofo-users mailing list
Podofo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/podofo-users
