www/proprietary proprietary-incompatibility.html

[Therese Godefroy]

CVSROOT:        /webcvs/www
Module name:    www
Changes by:     Therese Godefroy <th_g> 18/02/10 08:25:02

Added files:
        proprietary    : proprietary-incompatibility.html 

Log message:
        [RT #1268079] Add proprietary-incompatibility.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/proprietary-incompatibility.html?cvsroot=www&rev=1.1

Patches:
Index: proprietary-incompatibility.html
===================================================================
RCS file: proprietary-incompatibility.html
diff -N proprietary-incompatibility.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ proprietary-incompatibility.html    10 Feb 2018 13:25:01 -0000      1.1
@@ -0,0 +1,113 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.85 -->
+<title>Proprietary Incompatibility
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/server/gnun/initial-translations-list.html" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Proprietary Incompatibility</h2>
+
+<p><a href="/proprietary/proprietary.html">Other examples of proprietary 
malware</a></p>
+
+<p>The &ldquo;incompatibility&rdquo; category includes the use of secret
+formats or protocols in proprietary software. This directly blocks or
+hinders users from switching to any alternative program&mdash;and, in
+particular, from switching to free software which can liberate the
+device the software runs on.</p>
+
+<p>Apart from being deliberately anticompetitive, secret formats put users'
+digital data at risk. For instance, retrieval of old data will become very
+difficult if support for the proprietary software that can read it is
+discontinued.</p>
+
+<p>Another sort of incompatibility occurs when a system makes some 
+important operation which would be necessary for migrating data to any
+other system so cumbersome or so slow that it isn't doable for more than
+a small amount of data.</p>
+
+<ul>
+<li>
+<p>iWork (office software that runs on MacOS, iOS and iCloud) uses secret
+formats and <a href="https://en.wikipedia.org/wiki/IWork";>provides no means
+of converting them to or from Open Document Formats</a>. iWork formats
+have changed several times since they were first introduced. This may have
+had the effect of thwarting <a
+href="https://github.com/obriensp/iWorkFileFormat";>reverse engineering
+efforts</a>, thus preventing free software from fully supporting them.</p>
+
+<p>iWork formats are considered <a
+href="https://wiki.harvard.edu/confluence/download/attachments/204385883/Format%20profile%20-%20Apple%20iWork%20Pages%20v04.docx?version=1&amp;modificationDate=1459873751000&amp;api=v2";>
+unfit for document preservation</a>.</p>
+</li>
+
+<li>
+<p>In MacOS and iOS, the procedure for <a
+href="https://support.apple.com/guide/photos/export-photos-videos-and-slideshows-pht6e157c5f/mac";>
+converting images from the Photos format</a> to a free format is so tedious
+and time-consuming that users just give up if they have a lot of them.</p>
+</li>
+</ul>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.  Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright &copy; 2018 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
+Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2018/02/10 13:25:01 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>