Font Company Wielding DMCA Against Bit-Flipping
Roundeye writes: "Seems that AGFA Monotype is trying to stop Tom Murphy from distributing his embed tool. According to the lawyers, the pair of bits in a TrueType font which specify how a font should be embedded constitute a DMCA-worthy access control device. Tom's standing up to them because, 'Embedding bits do nothing to keep consumers from copying fonts' and 'Since the enactment of the DMCA, I have only ever run embed on fonts for which I own the copyright." He's even got his own haiku version of the software..."
Soon any "undefined/future use" bits on a devices will be retroactively defined as access/copyright control and used as an excuse to sue thru DMCA.
Sad.
Learning HOW to think is more important than learning WHAT to think.
Say goodbye to saving your work in the middle and coming back to it. Say goodbye, potentially, to backup software, since adding registry keys post-installation may be involved in copy control, and backup software would bypass that. Say goodbye to...well...computers. (Not that this hasn't been said before elsewhere, but...)
This flies in the face of science.
Is with the CDA, the entire law was not thrown out, just the parts that were questioned and found unconstitutional.
For any real effect, the trial court ruling has to be reviewed by an appeals court.
Fight Spammers!
Non-Parity memory outlawed due to the risk of alpha particles bit flipping true-type fonts!
If you could be told what you can see or read, then it follows that you could be told what to say or think - BoC
This raises a great point about the DCMA. If I have a company that produces a tool to help me create products I am ok. Now, if my tool is used by others to circumvent what they call protection am I liable?
2 .h tm
In this case preventing someone from embedding a font doesn't protect the font. The font can easily be included with the document. This is nuts.
The embedding bits were orginally designed to make things easier for people to *distribute* fonts, not impede the distribution.
Check out this from Microsoft:
http://www.microsoft.com/typography/embed/embed
The best quote:
"Most foundries and type designers set the embedding level of their fonts to Editable embedding allowed or Print & Preview embedding allowed. However, a few foundries set the embedding level to No embedding allowed. If you feel that embedding technology has a place within your organization, be sure to ask the type vendor about it before you part with any money."
They have a web form you can fil out here:
AGFA's Web form.
When they get bombarded with emails, they'll know that they're under the public eye. If this goes to court, I may be willing to donate a few dollars to assist ith legal fees.
"Derp de derp."
For those who haven't read the article, and think that the author of the program has made some complex circumvention device, here's a haiku description of the program from the author's webpage:
The OS/2 chunk
has a bit for embedding.
Set it to zero.
Grr! Arg!
Anyway, in case you're curious, I've been pushing their buttons a little bit, with the help of Dave Touretzky , and my current guess is that they have given up on me. (I haven't heard back since the letter I sent them that's on that page.) But I will be happy to go to court over this retarded case, and the EFF has informally offered to help if I do. ( Donate! )
In case you're interested, my fonts, which I've been making since 1993 (and which are free for you to use for practically anything) are at fonts.tom7.com .
Oh For Fuck's Sake.
What about hex-editors then?
What about sed? I'll be you could come up with a nifty program to twiddle some bits in the same manner.
And for those lawyers, I've got a couple of bits they can twiddle; my balls.
I hope Tom wins.
Humorless sig goes here.
Tom wrote "embed" in 1997, as stated in his emails. DMCA went into the books in 1998. So he wrote the program before the law even existed... How can you break a law before it's a law?
This guy has some really good points, this just appears to be another case of a corporation using the vaguely worded DMCA to try and push someone around. How's that saying go? "If you can't make a good product, sue someone that has"?
Everytime we see an example of the little guy getting threatened by the Big Evil, we Slashdotters have an orgy of analysis and in the end do absolutely nothing. Appeals to donate to the EFF are roundly issued but how many bother?
What Slashdot needs to do is have a Fund set up - basically, an Amazon click-to-pay or PayPal (or both) account setup on the front page. It shoudl be preset for $1 donations. Every time we have a YRO post on slashdot frontpage, the donate buttons shoudl be inserted into the comments page.
The idea is, make it EASY to donate, makie it quick, make the links impossible to miss and always appear in correct context. If I had such a link infront of me right now I'd click it.
Every time we see a case like this, we set up a fund and channel funds to the poor guy. And maybe Slashdot could channel a matching percentage to the EFF as a donation from teh advertising revenue.
There has to be a way to leverage the huge community numbers here into actual tangible pressure - and money is the best way.
Don't blame me - I voted for Howard Dean. http://dean2004.blogspot.com
This is not a case of "you can't do what you want to your own fonts".
Rather, this is a case of "while you can do what you want with your own fonts, you can't distribute a tool to let other people do what they want to their fonts without writing their own software".
It's still wrong and still probably outside the scope of the DMCA, but not quite as bleak as you state.
It's public domain. He obviously doesn't mind
/* location for checksum */ ; ; ; ; /* write checksum */
/*
* This program is for setting TTF files to Installable Embedding mode.
*
* Note that using this to embed fonts which you are not licensed to embed
* does not make it legal.
*
* This code was written by Tom Murphy 7, and is public domain. Use at your
* own risk...
*/
#include <stdio.h>
#include <stdlib.h>
void fatal();
int main (int argc, char**argv) {
FILE * inways;
if (argc != 2)
printf("Usage: %s font.ttf\n\nPublic Domain software by Tom 7. Use at your own risk.\n",argv[0]);
else if (inways = fopen(argv[1],"rb+")) {
int a,x;
char type[5];
type[4]=0;
fseek(inways,12,0);
for (;;) {
for (x=0;x<4;x++) if (EOF == (type[x] = getc(inways))) fatal();
if (!strcmp(type,"OS/2")) {
int length;
unsigned long loc, fstype, sum=0;
loc=ftell(inways);
for (x=4;x--;) if (EOF == getc(inways)) fatal();
fstype = fgetc(inways) << 24;
fstype |= fgetc(inways) << 16;
fstype |= fgetc(inways) << 8
fstype |= fgetc(inways)
length = fgetc(inways) << 24;
length |= fgetc(inways) << 16;
length |= fgetc(inways) << 8
length |= fgetc(inways)
/* printf("fstype: %d length: %d\n",fstype,length);*/
if (fseek(inways,fstype+8,0)) fatal();
fputc(0,inways);
fputc(0,inways);
fseek(inways,fstype,0);
for (x=length;x--;)
sum += fgetc(inways);
fseek(inways,loc,0);
fputc(sum>>24,inways);
fputc(255&(sum>>16),inways);
fputc(255&(sum>>8), inways);
fputc(255&sum , inways);
fclose(inways);
exit(0);
}
for (x=12;x--;) if (EOF == getc(inways)) fatal();
}
} else
printf("I wasn't able to open the file %s.\n", argv[1]);
}
void fatal() { fprintf(stderr,"Malformed TTF file.\n");
exit(-1); }
Do you even lift?
These aren't the 'roids you're looking for.
You obviously don't work in the design field do you?
Fonts aren't "freely distributed" in most cases. Fonts usually do accompany a piece sent to the printer to ensure the printer can reproduce the typeface in the design. But the printer must remove the fonts from their system if they do not have rights to them. Fonts you see in print are nearly always copyrighted due to the demanding nature of making a good, legible and proper typeface.
Check out this book.
Did you read my response?
In order for embed to be covered by the DMCA, the program has to be primarily designed for circumvention. Circumvention only occurs when the act is without the authority of the copyright holder. In this case, I am the copyright holder, so of course I grant myself authority to modify the bits!
(There are several other reasons why their argument doesn't hold that I give, but this is the strongest...) I think their legal argument is faulty.
Check what IP the lawyer uses.
:-)
Use a Apache rewrite rule to serve up a version of the web page without the link to the program, for the lawyer's subnet.
Solved.
There's 10 types of people in this world, those who understand binary and those who don't.
Probably not. A device has to be primarily designed for the purpose of circumvention, or marketed for circumvention.
Most importantly, though, "circumvention" only occurs if it is done without the authority of the copyright holder. If a format is open, and therefore many people (including the author of the program, perhaps) have reason to modify their works with the program, they of course have authority -- so it would be hard to argue that the device is designed "primarily" for circumvention. That's my main argument for this Embed thing.
Perhaps that is the real downfall of the DMCA...?
I don't mind. It's also in the public domain, so I can't stop you.
But, it's important that you are not acting in concert with me -- your actions are independent. (That also of course makes it harder for them to use legal measures to get it taken down.)
Writing new programs that do the same thing would also make it quite annoying for them...
Here's an interesting tidbit. .)
As it turns out, fonts cannot be copyrighted in the US. Only the truetype "programs" that generate them can. (See comp.fonts FAQ
Therefore, it would almost certainly be legal to write a program that takes copyrighted truetype "programs" as input, and produces equivalent programs (that is, they generate the same typeface) that are not copyrighted. It would also need to change the names to avoid trademark infringement. If I did this, and also changed the embedding bit, would that not put me in the clear of any possible DMCA claim?
If Tom wants to make his fonts freely available to others, and uses his software to toggle bits on his fonts, fine.
But, it clear from comments here that at least some people are using the program to illegally embeed fonts in documents, such as PDFs. And yes, this is illegal. Embeed fonts are a good thing, I like them, but only if I own them and the redistribution rights or can freely do so. This is why default system fonts are so often used for such documents. So that the fonts can be freely passed around.
Like any other piece of software, font design and typograph requires work to create. And its not drudge labor either, it takes both skill and creative ability. Commerical font houses pay people to create these, and then sell their work. Usually, such fonts are licenses so that people can use them to print paper documents, or view other documents on systems where the owners have also licensed the font. Don't have the font? Buy it or go read something else.
Using a propitary font on a website, and redistributing it to people looking at your site is piracy, clear and simple. No ifs, ands, or buts.
The font industry has adopted a very reasonable approach till now. No heavy handed DRM, just a couple of bits and the trust that software will honor them. This is convient for consumers and protects the people who work to create the things we use.
The DMCA might not be entirely appropriate here, and perhaps the case should be tossed on technicalities. But whatever the non-infringing uses and the authors own utility for the program, the people on slashdot have made it clear that the non-infringing use is pretty marginal to the illegal one.
A shame. Perhaps the author should look at writting a font editor of his own. One that defaults to free access for new fonts, and allow increasing security, but not granting new permissions on commercial fonts. This is a fair method of handling the problem, one that appears to have previously been used successfully without resorting to more draconian copyright protections.
Jason Denton Colorado State University [Thoughs and comments are my own, and not reflective of CSU]
comp.fonts FAQ: Are fonts copyrightable?
Looks to me like truetype fonts (and similar formats that have program-like logic included) are copyrightable, but typefaces in general (including the font after rendering) are not.
314-15-9265
That's like outlawing guns because someone might get shot!
Isn't that what they've been doing gradually for the past few years now?
-- Mal: "Well they tell you: never hit a man with a closed fist. But it is, on occasion, hilarious."
Paul F. Stack
Member
Stack & Filpi,
Chartered
Suite 411, 140 South Dearborn Street
Chicago, Illinois 60603-5298
(Cook Co.)
Telephone: 312-782-0690
Facsimile: 312-782-0936
Here's his email addy. AOL, kinda figures, don't it?
pstack7901@aol.com
KFG
Realnetworks, Inc. v. Streambox, Inc.
Disclaimer: I am not a lawyer. I do, however, know the DMCA very well, since I've been worried for many years about being sued under the DMCA for my anticensorware workSig: What Happened To The Censorware Project (censorware.org)
Well, this calls for action. This clueless lawyer is probably going to get an order from a kangaroo court, maybe from Kaplan, the judge who ruled that publishing a link on 2600.org was an act of DVD piracy. If this happens, Tom Murphy is going to face huge legal costs.
Since this is really bothering me a lot, I went to EFF's site and made a small donation. Come on, do it now! Do something for your rights now!
If the EFF starts getting donations each time these bozos fling the DMCA around, then maybe they'll understand.
Do you feel safe? Huh uh. Want to admire the handywork of Lewis Kaplan against your right to put a link (a freakin' link!) into your web site? Feel free to bask in his wisdom.
Got the message? Donate now.
Hodie mi, cras tibi - Today it's me, tomorrow it's you (famous last words of a Roman dragged to his execution by his tyrannic government.)
--
Mad science! Robots! Underwear! Cute girls! Full comic online! http://www.girlgeniusonline.com/
Therefore, it would almost certainly be legal to write a program that takes copyrighted truetype "programs" as input, and produces equivalent programs (that is, they generate the same typeface) that are not copyrighted.
Such a program would have no different legal status from a C preprocessor; a U.S. federal court would probably consider the output to be a derivative work of the input. 17 USC 106 gives the copyright owner of a font file a limited exclusive right to prepare derivative works from a copyrighted work.
Will I retire or break 10K?
Isn't it ridiculous? This supposed "access control" is nothing if it isn't honored. It's like when a mime is trapped in a box. The mime is only trapped in the box so long as he continues to pretend that there is a box he's trapped in. If the mime gets bored and wants to leave, he doesn't 'circumvent' the box, he just stops prentending it exists.
Or it's like I put up a sign in front of my house that says "Property surrounded by impenetrable force field". If someone ignores the sign, I may be able to accuse them of trespassing, but I sure as hell couldn't accuse them of breaking and entering because they had to break through my forcefield to trespass! Well, I could, but I'd be branded a looney the moment the words left my mouth. I can only -hope- something similar happens here.
The enemies of Democracy are
I searched the copyright office's web site for "fonts" and stumbled across this letter:
p df
http://www.loc.gov/copyright/1201/comments/004.
It's a comment submitted by Aladdin Enterprises (the makers of ghostscript) during the Copyright Office's review of the DMCA two years ago. It addresses almost exactly the current situation:
"...There is, in fact, a commercially important situation where this is currently the case. A software package called Fontographer is used very widely for creating TrueType font files. A bug in Fontographer causes it to improperly mark the fonts it produces in a way that causes certain other widely used software packages to consider that the font may not be embedded in documents that use the font. This incorrect marking happens by default, contrary to the wishes of the font author. The authors of Fontographer have been unresponsive to users and authors and have not fixed this problem. Thus a situation has been created where the author of the font wishes to allow users to embed it, but users who remove the protection marking (which is extremely simple technically -- it involves changing one easily-located bit in the font) will be in violation of the law."
Who would have thought that Richard Stallman was correct all these years regarding free-as-in-speech software? How many of you just thought he was a paranoid lunatic?
From The Right To Read:
- Dan would later learn that there was a time when anyone could have debugging tools. There were even free debugging tools available on CD or downloadable over the net. But ordinary users started using them to bypass copyright monitors, and eventually a judge ruled that this had become their principal use in actual practice. This meant they were illegal; the debuggers' developers were sent to prison.
--Jeff++... In 2047, Frank was in prison, not for pirate reading, but for possessing a debugger.
ipv6 is my vpn
This means that none of your fonts (even those created by yourself) can be embedded in PDF.
So, every font producer probably has written an EMBED-like program for themselves. I know 'cause I've written it twice: Sometime in 1992, but then lost the source code, and again a couple of weeks ago.
Agfa/ITC/Monotype/Letraset/whateverCorpWeAreGobbli ngUpThisWeek are bullying Tom around for a program which has a predominant legitimate use for every font producer.
Oh, BTW, Macromedia will never fix the endless amount of bugs in Fontographer. Development is on hold, the last version was published eight years ago. Click here for my take on this.
-Martin
SoftMaker Office for Windows|Linux|Android