Source files of fsfe.org, pdfreaders.org, freeyourandroid.org, ilovefs.org, drm.info, and test.fsfe.org. Contribute: https://fsfe.org/contribute/web/ https://fsfe.org
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

pdfreaders.en.xhtml 7.2KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165
  1. <?xml version="1.0" encoding="UTF-8" ?>
  2. <html>
  3. <head>
  4. <title>PDFreaders - Free Software PDF Readers - FSFE</title>
  5. </head>
  6. <body class="article" microformats="h-entry" id="pdfreaders">
  7. <h1 class="p-name">Free Software PDF Readers </h1>
  8. <div class="captioned right" style="max-width: 650px; width: 53%">
  9. <a href="/campaigns/pdfreaders/highway.png">
  10. <img src="/campaigns/pdfreaders/highway.png" alt="highway" width="100%"/>
  11. </a>
  12. </div>
  13. <div class="e-content">
  14. </div>
  15. <div class="p-summary">
  16. <p>What would you think about a sign on the highway saying “You need a
  17. Toyota to drive on this road. Contact your Toyota dealer for a gratis
  18. test drive -- Your Government”? When it comes to software that opens PDF
  19. files, many public sector organisations do this every day.</p>
  20. </div>
  21. <p>With the pdfreaders.org campaign we have turned the spotlight on
  22. government organisations who behave in this way, exposing how frequent such
  23. advertisements for non-free software are. With the help of activists across
  24. Europe, <a href="/campaigns/pdfreaders/follow-up.html">we contacted</a> these
  25. organisations and explained to them how to improve their websites so that
  26. they respect our freedom.</p>
  27. <h2>Why should we care?</h2>
  28. <p>Even when a certain software is given away for free, the company behind it
  29. can have an economic gain: promoting that software means prioritising a
  30. specific company. Public bodies should not promote any specific private
  31. company, instead they should promote equality and choice on the software
  32. market. That is why FSFE and its volunteers intervened to fix the
  33. problem.</p>
  34. <p>This campaign was based on three core principles we support at FSFE:</p>
  35. <ul>
  36. <li>Neutrality - Public institutions should not engage in advertising</li>
  37. <li>Freedom - Public institutions should not ask citizens to use non-free
  38. Software</li>
  39. <li><a href="/activities/os/def.html">Open Standards</a> – The versions of
  40. the PDF format which are Open Standards can be implemented by all PDF
  41. readers</li>
  42. </ul>
  43. <h2>What did we achieve?</h2>
  44. <div class="captioned left">
  45. <a href="/campaigns/pdfreaders/finanzBrandenburg.png">
  46. <img src="/campaigns/pdfreaders/finanzBrandenburg_p.png" alt="Finance ministry Brandenburg" /></a>
  47. <footer>
  48. <p>Example from Germany with the advertisement</p>
  49. </footer>
  50. </div>
  51. <p>Every day, public institutions advertise non-free software on their
  52. websites. With the help of our Fellows and of hundreds other Free Software
  53. activists, we collected <a
  54. href="http://fsfe.org/campaigns/pdfreaders/buglist.html">2104 bug
  55. reports</a> over the course of one month from every country in Europe,
  56. and also nine countries outside of Europe. </p>
  57. <p>Next, the FSFE and its volunteers sent letters to all the public
  58. administrations on our list asking them to either remove their advertising
  59. for proprietary software, or to at least run equal advertising for Free
  60. Software, so that users of their websites realise that they have a choice. In
  61. response, we received a lot of positive feedback from the institutions
  62. thanking us for our letters.</p>
  63. <p>Now, several years, and thousands of letters later, the FSFE has closed
  64. the campaign. Thanks to all the dedicated Free Software activists who helped
  65. contact institutions, we can proudly announce that we were able to remove
  66. advertisements for proprietary PDF readers in 1125 of the 2104 public
  67. administration websites (53%).</p>
  68. <div class="captioned right">
  69. <a href="/campaigns/pdfreaders/BrandenburgResolved.png">
  70. <img src="/campaigns/pdfreaders/BrandenburgResolved_p.png" alt="resolved" /></a>
  71. <footer>
  72. <p>The same website after they fixed it</p>
  73. </footer>
  74. </div>
  75. <p>Furthermore, we were able to push for a change at both national and
  76. international levels.</p>
  77. <ul>
  78. <li> In Germany, <a
  79. href="http://gruen-digital.de/2012/03/document-freedom-day-kleine-anfrage-zur-werbung-fuer-adobe-reader-eingereicht/">national
  80. parties</a> gave statements in favour of free PDF readers and the
  81. German Government itself has recommended the usage of our text snippet
  82. in their <a
  83. href="http://www.cio.bund.de/Web/DE/Architekturen-und-Standards/Migrationsleitfaden-und-Migrationshilfen/migrationsleitfaden_node.html">migration
  84. guide</a>. FSFE's coordinator for Germany, Max Mehl, <a href="http://blog.mehl.mx/2015/german-government-wants-authorities-to-advertise-pdfreaders/">covers it</a>
  85. in more detail on his blog.</li>
  86. <li>In the EU: the European Parliament <a
  87. href="/campaigns/pdfreaders/parliamentary-questions-eu.html">directly
  88. asked</a> the European Commission what were the reasons for advertising
  89. a specific software and which steps were taken to solve this problem.</li>
  90. <li> In 2011 one of our pdfreaders.org coordinators, <a
  91. href="http://blogs.fsfe.org/polina/2015/09/10/free-pdf-reader-for-the-web-browser/">
  92. Hannes Hauswedell, was in contact with Google</a>, asking them to
  93. release the PDF reader included in their Chrome browser as Free Software.
  94. Finally, in May 2014 the <a
  95. href="https://twitter.com/nasko/status/469595752734269440"> pdfium
  96. sources were published openly</a>, and while FSFE's enquiry might not
  97. have been the only reasons they were released, it marks an important
  98. change for the widespread adoption of Free Software PDF readers.</li>
  99. </ul>
  100. <p>In addition to contacting public institutions to resolve the issue, FSFE
  101. also collected signatures from 90 organisations, 63 businesses, and 2731
  102. individuals who demanded equal access for Free Software PDF readers. This
  103. wide-ranging support also demonstrated the popularity of the campaign
  104. overall.</p>
  105. <h2>What's next?</h2>
  106. <p>The Free Software movement is, above all, supported by its community; we
  107. always need your help to continue to help promote free PDFreaders, and
  108. together we can make a difference for the future of Free Software! We
  109. encourage you to continue to <a href="/campaigns/pdfreaders/letter.html">use
  110. our template and send letters</a> or emails to public bodies that are still
  111. advertising for proprietary software and closed standards. We also have a
  112. link for tips on <a href="/campaigns/pdfreaders/follow-up.html">how to
  113. follow-up with the relevant institution</a>. This is a great (and easy)
  114. activity for a local Free Software groups to spread Free Software knowledge
  115. in the public administration.</p>
  116. </body>
  117. <sidebar GoingFurther="pdfreaders" promo="about-fsfe">
  118. <h3>More on PDF Readers</h3>
  119. <ul>
  120. <li><a href="/campaigns/pdfreaders/follow-up.html">How to contact institutions</a></li>
  121. <li><a href="/campaigns/pdfreaders/buglist.html">List of reported institutions</a></li>
  122. <li><a href="/campaigns/pdfreaders/petition.html">The petition</a></li>
  123. <li><a href="/campaigns/pdfreaders/letter.html">Model Letter</a></li>
  124. <li><a href="http://www.pdfreaders.org">List of Free Software PDF readers</a></li>
  125. </ul>
  126. </sidebar>
  127. <followup>subscribe-nl</followup>
  128. <tags>
  129. <tag>PDFreaders</tag>
  130. <tag content="Public administration">PublicAdministration</tag>
  131. <tag content="campaign">Campaigns</tag>
  132. </tags>
  133. <timestamp>$LastChangedDate$ $Author$ </timestamp>
  134. </html>