On 8/25/20 3:46 AM, Andrey Semashev via Boost wrote:
On 2020-08-24 22:40, Zach Laine via Boost wrote:
On Mon, Aug 24, 2020 at 2:31 PM Andrey Semashev via Boost
wrote: On 2020-08-24 21:24, Peter Dimov via Boost wrote:
Andrey Semashev wrote:
But if it indeed means binary form as well then, alas, no Unicode in Boost.
It does, but I'm pretty sure the Unicode consortium isn't going to go after us for this specific use (using the data files to generate code that is necessary to implement the functionality specified in the standard.)
It doesn't matter how likely it is. This isn't just about us, but also about our users.
One other option would be to ask Unicode Inc. for a permission to use Unicode data in binary form without the requirement to present the license.
Why is this suddenly a problem if Boost.Spirit has been doing it for years?
Because apparently noone knew they were doing this. It may well become a problem of Boost.Spirit now.
Personally, I'm still not sure there is a license incompatibility, until a lawyer comments.
Oh my! Michael Caisse brought this to my attention. I too was not aware that this will cause some license problems. The development of the unicode parts of Spirit was not a secret. Development proceeded in full public view and no one pointed out this issue, until now. It never occurred to me that this is a violation. I will defer to consensus in the Boost community. I too would like to hear what a lawyer says about this. Regards, -- Joel de Guzman