Lior Kaplan: Hebrew, Perl and a License Hell
Three months ago Gal-Gur Arie asked me to package a Perl module named Locale::Hebrew. The goal is to enable Hebrew support in xmltv which uses a Perl script to pull the Israeli TV schedule. See #432748.
Gal’s request falls under my Debian Hebrew category, otherwise I would refer his request to the Debian Perl Group.
I started to work on the package, and reached the part of creating the debian/copyright file. In the Perl code, everything was OK, as it’s licensed under the Artistic License. But then I notice a bidi.c file with the following “license”:
Source code in this file and the header file may be distributed free of charge by anyone, as long as full credit is given and any and all liabilities are assumed by the recipient.But it also had this:
Copyright (C) 1999, ASMUS, Inc. All Rights ReservedAs the “license” isn’t free, and the previous line pretty much makes that clear, I couldn’t upload the package to the archive. Maybe to non-free but I prefer that would be my last option. I was able to contact the copyright holders, and ask for clearing the license. Preferably with re-licensing the code with the GPL or other OSI approved license. Asmus Freytag answered me that there’s an updated version of the file in unicode.org with a proper references to a license, and suggested that I should check if it that’s OK for me. That license isn’t a free software license, but has en exclusion clause for certain files:
Permission is hereby granted, free of charge, to any person obtaining a copy of the Unicode data files and any associated documentation (the “Data Files”) or Unicode software and any associated documentation (the “Software”) to deal in the Data Files or Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Data Files or Software, and to permit persons to whom the Data Files or Software are furnished to do so, provided that (a) the above copyright notice(s) and this permission notice appear with all copies of the Data Files or Software, (b) both the above copyright notice(s) and this permission notice appear in associated documentation, and (c) there is clear notice in each modified Data File or in the Software as well as in the documentation associated with the Data File(s) or Software that the data or software has been modified.To me, this seems free according to the DFSG. So I got a second opinion at debian-legal just to be sure. Well, now that the licensing issues are over, I needed to check that the software can work with the new bidi.c file. Audrey Tang (the original upstream) was kind enough to help with the testing, but here tests showed that too much have changed in the new bidi.c file, and the program doesn’t build correctly. So I’m back in square one… I got back to Asmus Freytag for a license change, this time asking for the unicode.org license. Asmus didn’t approve my request, and referred me to unicode.org for an answer. Full correspondence is available in the liblocale-hebrew-perl’s ITP. The problem is that I can’t be sure the file originated at unicode.org, as there isn’t any reference to them. And anyway, any license change should be done by Asmus Inc. and not unicode.org. Any one with contacts in Unicode, Inc. ? The best solution would probably be writing a Perl bindings around libfribidi as was done for Python. The problem is that I don’t have a volunteer for that. Bummer.
My personal email account was spammed by
Jennifer Kirkham-Sandy
(Phone 0800 6 121 151)
of
Total Language Solutions Limited,
3 The Courtyard,
New North Road,
Exeter EX4 4EP,
Devon.
Registered number (England and Wales)
at the above address: 03933805.
They seemed to be using a service called qwertywordmarketing.
I've reported it to the hosting company,
so we'll see what happens.
After Argentina-France on the first day, that one was planned to be one of
the few big matches of first round.
Of course, after the game won by South Africa (36-0), that seems pretty
silly to say...
The Springboks were definitely better than England, in all parts of the
game. What stunned me, particularly after 
I'm thinking about setting up an ARM developer machine, with a twist: I want to have JTAG accessible remotely. Obviously, that is a bit of a security risk if applied to a normal machine, so I'd probably build some system allowing you to upload and run images.
I completely agree with
Scientific papers always have a “related works” section, where the authors describe how the work they are presenting compares with what others did. In the Free Software world, this is nearly non-existent: in a way, it seems that many of us are thinking of their projects as competing products, fighting for market share. On a project web page, I would love to read something like:
Argh... I know it seems like I've given up on blogging entirely, but that's not the case. I've just been spending a lot of time working on Evan Prodromou instead of on evan.prodromou.name, which has been a whole different kind of world.
I'm mostly poking my head up to point to an article in the
Slightly used
I cannot build the new upstream rtorrent package (at least not as should been built) because of 


Just completed the migration of the next version of
If you experience the following error: