Author: phobos Date: 2011-09-16 02:32:04 +0000 (Fri, 16 Sep 2011) New Revision: 25082 Modified: website/trunk/eff/en/tor-dmca-response.wml Log: fix the odd character encodings. Modified: website/trunk/eff/en/tor-dmca-response.wml =================================================================== --- website/trunk/eff/en/tor-dmca-response.wml 2011-09-16 02:26:27 UTC (rev 25081) +++ website/trunk/eff/en/tor-dmca-response.wml 2011-09-16 02:32:04 UTC (rev 25082) @@ -14,7 +14,7 @@ <p>Note to Tor relay operators: In this litigious era, anyone providing routing services may face copyright complaints for transmitted content. Fortunately, the Digital Millennium Copyright Act safe harbors should -provide protections from many of them�both to you and to your upstream +provide protections from many of them both to you and to your upstream provider. If your Internet host forwards a DMCA copyright complaint to you, you can use this template to write a response, though you will need to customize it to your situation. Please also ensure all the statements @@ -56,7 +56,7 @@ run.</p> <p>As you know, the DMCA creates four "safe harbors" for service providers to protect them from copyright liability for the acts of their -users, when the ISPs fulfill certain requirements. (17 U.S.C. � 512) The +users, when the ISPs fulfill certain requirements. (17 U.S.C. § 512) The DMCA's requirements vary depending on the ISP's role. You may be familiar with the "notice and takedown" provisions of section 512(c) of the DMCA; however, those do not apply when an ISP merely acts as a @@ -80,7 +80,7 @@ terminates subscribers who are repeat infringers. The notification you received is certainly not proof of the "repeat infringement" that is required under the law before you need to terminate my account. In fact, -it�s not even proof of any copyright infringement; a notice claiming +it's not even proof of any copyright infringement; a notice claiming infringement is not the same as a determination of infringement. I have not infringed any copyrights and do not intend to do so. Therefore, you should continue to be protected under the DMCA 512(a) safe harbor