www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/philosophy/po when_free_software_isnt_pract...


From: Pavel Kharitonov
Subject: www/philosophy/po when_free_software_isnt_pract...
Date: Mon, 16 Mar 2015 18:16:40 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     Pavel Kharitonov <ineiev>       15/03/16 18:16:40

Removed files:
        philosophy/po  : 
                         
when_free_software_isnt_practically_superior.fr-en.html 
                         when_free_software_isnt_practically_superior.pot 
                         
when_free_software_isnt_practically_superior.ru-en.html 
                         when_free_software_isnt_practically_superior.ru.po 
                         when_free_software_isnt_practically_superior.translist 

Log message:
        Remove spurious files.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/when_free_software_isnt_practically_superior.fr-en.html?cvsroot=www&r1=1.1&r2=0
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/when_free_software_isnt_practically_superior.pot?cvsroot=www&r1=1.1&r2=0
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/when_free_software_isnt_practically_superior.ru-en.html?cvsroot=www&r1=1.1&r2=0
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/when_free_software_isnt_practically_superior.ru.po?cvsroot=www&r1=1.1&r2=0
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/when_free_software_isnt_practically_superior.translist?cvsroot=www&r1=1.1&r2=0

Patches:
Index: when_free_software_isnt_practically_superior.fr-en.html
===================================================================
RCS file: when_free_software_isnt_practically_superior.fr-en.html
diff -N when_free_software_isnt_practically_superior.fr-en.html
--- when_free_software_isnt_practically_superior.fr-en.html     16 Mar 2015 
15:59:38 -0000      1.1
+++ /dev/null   1 Jan 1970 00:00:00 -0000
@@ -1,187 +0,0 @@
-<!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: 1.77 -->
-<title> When Free Software Isn't (Practically) Better - GNU Project - Free 
Software Foundation</title>
-<!--#include 
virtual="/philosophy/po/when_free_software_isnt_practically_better.translist" 
-->
-<!--#include virtual="/server/banner.html" -->
-<h2> When Free Software Isn't (Practically) Better</h2>
-
-<p>The Open Source Initiative's mission statement reads, &ldquo;Open source
-is a development method for software that harnesses the power of
-distributed peer review and transparency of process. The promise of
-open source is better quality, higher reliability, more flexibility,
-lower cost, and an end to predatory vendor lock-in.&rdquo;</p>
-
-<p>For more than a decade now, the Free Software Foundation has argued
-against this &ldquo;open source&rdquo; characterization of the free software
-movement. Free software advocates have primarily argued against this
-framing because &ldquo;open source&rdquo; is an explicit effort to deemphasize
-our core message of freedom and obscure our movement's role in the
-success of the software we have built. We have argued that &ldquo;open
-source&rdquo; is bad, fundamentally, because it attempts to keep people from
-talking about software freedom. But there is another reason we should
-be wary of the open source framing. The fundamental open source
-argument, as quoted in the mission statement above, is often
-incorrect.</p>
-
-<p>Although the Open Source Initiative suggests &ldquo;the promise of open
-source is better quality, higher reliability, more flexibility,&rdquo; this
-promise is not always realized. Although we do not often advertise the
-fact, any user of an early-stage free software project can explain
-that free software is not always as convenient, in purely practical
-terms, as its proprietary competitors. Free software is sometimes low
-quality. It is sometimes unreliable. It is sometimes inflexible. If
-people take the arguments in favor of open source seriously, they must
-explain why open source has not lived up to its &ldquo;promise&rdquo; and 
conclude
-that proprietary tools would be a better choice. There is no reason we
-should have to do either.</p>
-
-<p>Richard Stallman speaks to this in his article on <a
-href="/philosophy/open-source-misses-the-point.html">Why
-Open Source Misses the Point</a> when he explains, &ldquo;The idea of open
-source is that allowing users to change and redistribute the software
-will make it more powerful and reliable. But this is not
-guaranteed. Developers of proprietary software are not necessarily
-incompetent. Sometimes they produce a program that is powerful and
-reliable, even though it does not respect the users' freedom.&rdquo;</p>
-
-<p>For open source, poor-quality software is a problem to be explained
-away or a reason to eschew the software altogether. For free software,
-it is a problem to be worked through. For free software advocates,
-glitches and missing features are never a source of shame.
-Any piece of free software that respects users' freedom has a strong
-inherent advantage over a proprietary competitor that does not. Even
-if it has other issues, free software always has freedom.</p>
-
-<p>Of course, every piece of free software must start somewhere. A brand-new
-piece of software, for example, is unlikely to be more featureful
-than an established proprietary tool. Projects
-begin with many bugs and improve over time. While open
-source advocates might argue that a project will grow into usefulness
-over time and with luck, free software projects represent important
-contributions on day one to a free software advocate. Every piece of
-software that gives users control over their technology is a step
-forward. Improved quality as a project matures is the icing on the
-cake.</p>
-
-<p>A second, perhaps even more damning, fact is that the collaborative,
-distributed, peer-review development process at the heart of the
-definition of open source bears little resemblance to the practice of
-software development in the vast majority of projects under free (or
-&ldquo;open source&rdquo;) licenses.</p>
-
-<p>Several academic studies of free software hosting sites <a
-href="http://sf.net";>SourceForge</a> and <a
-href="http://sv.gnu.org";>Savannah</a> have shown what many free
-software developers who have put a codebase online already know
-first-hand. The vast majority of free software projects are not
-particularly collaborative. The median number of contributors to a
-free software project on SourceForge?  One. A lone
-developer. SourceForge projects at the ninety-fifth percentile by
-participant size have only five contributors. More than half of these
-free software projects&mdash;and even most projects that have made several
-successful releases and been downloaded frequently, are the work of a
-single developer with little outside help.</p>
-
-<p>By emphasizing the power of collaborative development and &ldquo;distributed
-peer review,&rdquo; open source approaches seem to have very little to say
-about why one should use, or contribute to, the vast majority of free
-software projects. Because the purported benefits of collaboration
-cannot be realized when there is no collaboration, the vast majority
-of free development projects are at no technical advantage with respect to a
-proprietary competitor.</p>
-
-<p>For free software advocates, these same projects are each seen as
-important successes. Because every piece of free software respects its
-users' freedom, advocates of software freedom argue that each piece of
-free software begins with an inherent ethical advantage over
-proprietary competitors&mdash;even a more featureful one. By emphasizing
-freedom over practical advantages, free software's advocacy is rooted
-in a technical reality in a way that open source is often not. When
-free software is better, we can celebrate this fact. When it is not,
-we need not treat it as a damning critique of free software advocacy
-or even as a compelling argument against the use of the software in
-question.</p>
-
-<p>Open source advocates must defend their thesis that freely developed
-software should, or will with time, be better than proprietary
-software. Free software supporters can instead ask, &ldquo;How can we make
-free software better?&rdquo; In a free software framing, high quality software
-exists as a means to an end rather than an end itself. Free software
-developers should strive to create functional, flexible software that
-serves its users well. But doing so is not the only way to make steps
-toward solving what is both an easier and a much more profoundly
-important goal: respecting and protecting their freedom.</p>
-
-<p>Of course, we do not need to reject arguments that collaboration can
-play an important role in creating high-quality software. In many of
-the most successful free software projects, it clearly has done
-exactly that. The benefits of collaboration become something to
-understand, support, and work towards, rather than something to take
-for granted in the face of evidence that refuses to conform to
-ideology.</p>
-
-</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 3.0 US.  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; 1999-2011 Benjamin Mako Hill</p>
-
-<p>This page is licensed under a <a rel="license"
-href="http://creativecommons.org/licenses/by-sa/3.0/us/";>Creative
-Commons Attribution-Share Alike 3.0 United States License</a>.</p>
-
-<!--#include virtual="/server/bottom-notes.html" -->
-
-<p class="unprintable">Updated:
-<!-- timestamp start -->
-$Date: 2015/03/16 15:59:38 $
-<!-- timestamp end -->
-</p>
-</div>
-</div>
-</body>
-</html>
-

Index: when_free_software_isnt_practically_superior.pot
===================================================================
RCS file: when_free_software_isnt_practically_superior.pot
diff -N when_free_software_isnt_practically_superior.pot
--- when_free_software_isnt_practically_superior.pot    16 Mar 2015 15:59:39 
-0000      1.1
+++ /dev/null   1 Jan 1970 00:00:00 -0000
@@ -1,227 +0,0 @@
-# LANGUAGE translation of 
http://www.gnu.org/philosophy/when_free_software_isnt_practically_better.html
-# Copyright (C) YEAR Free Software Foundation, Inc.
-# This file is distributed under the same license as the original article.
-# FIRST AUTHOR <address@hidden>, YEAR.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: when_free_software_isnt_practically_better.html\n"
-"POT-Creation-Date: 2014-03-14 04:36+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <address@hidden>\n"
-"Language-Team: LANGUAGE <address@hidden>\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=CHARSET\n"
-"Content-Transfer-Encoding: ENCODING"
-
-#. type: Content of: <title>
-msgid ""
-"When Free Software Isn't (Practically) Better - GNU Project - Free Software "
-"Foundation"
-msgstr ""
-
-#. type: Content of: <h2>
-msgid "When Free Software Isn't (Practically) Better"
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"The Open Source Initiative's mission statement reads, &ldquo;Open source is "
-"a development method for software that harnesses the power of distributed "
-"peer review and transparency of process. The promise of open source is "
-"better quality, higher reliability, more flexibility, lower cost, and an end "
-"to predatory vendor lock-in.&rdquo;"
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"For more than a decade now, the Free Software Foundation has argued against "
-"this &ldquo;open source&rdquo; characterization of the free software "
-"movement. Free software advocates have primarily argued against this framing "
-"because &ldquo;open source&rdquo; is an explicit effort to deemphasize our "
-"core message of freedom and obscure our movement's role in the success of "
-"the software we have built. We have argued that &ldquo;open source&rdquo; is "
-"bad, fundamentally, because it attempts to keep people from talking about "
-"software freedom. But there is another reason we should be wary of the open "
-"source framing. The fundamental open source argument, as quoted in the "
-"mission statement above, is often incorrect."
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"Although the Open Source Initiative suggests &ldquo;the promise of open "
-"source is better quality, higher reliability, more flexibility,&rdquo; this "
-"promise is not always realized. Although we do not often advertise the fact, "
-"any user of an early-stage free software project can explain that free "
-"software is not always as convenient, in purely practical terms, as its "
-"proprietary competitors. Free software is sometimes low quality. It is "
-"sometimes unreliable. It is sometimes inflexible. If people take the "
-"arguments in favor of open source seriously, they must explain why open "
-"source has not lived up to its &ldquo;promise&rdquo; and conclude that "
-"proprietary tools would be a better choice. There is no reason we should "
-"have to do either."
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"Richard Stallman speaks to this in his article on <a "
-"href=\"/philosophy/open-source-misses-the-point.html\">Why Open Source "
-"Misses the Point</a> when he explains, &ldquo;The idea of open source is "
-"that allowing users to change and redistribute the software will make it "
-"more powerful and reliable. But this is not guaranteed. Developers of "
-"proprietary software are not necessarily incompetent. Sometimes they produce "
-"a program that is powerful and reliable, even though it does not respect the "
-"users' freedom.&rdquo;"
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"For open source, poor-quality software is a problem to be explained away or "
-"a reason to eschew the software altogether. For free software, it is a "
-"problem to be worked through. For free software advocates, glitches and "
-"missing features are never a source of shame.  Any piece of free software "
-"that respects users' freedom has a strong inherent advantage over a "
-"proprietary competitor that does not. Even if it has other issues, free "
-"software always has freedom."
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"Of course, every piece of free software must start somewhere. A brand-new "
-"piece of software, for example, is unlikely to be more featureful than an "
-"established proprietary tool. Projects begin with many bugs and improve over "
-"time. While open source advocates might argue that a project will grow into "
-"usefulness over time and with luck, free software projects represent "
-"important contributions on day one to a free software advocate. Every piece "
-"of software that gives users control over their technology is a step "
-"forward. Improved quality as a project matures is the icing on the cake."
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"A second, perhaps even more damning, fact is that the collaborative, "
-"distributed, peer-review development process at the heart of the definition "
-"of open source bears little resemblance to the practice of software "
-"development in the vast majority of projects under free (or &ldquo;open "
-"source&rdquo;) licenses."
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"Several academic studies of free software hosting sites <a "
-"href=\"http://sf.net\";>SourceForge</a> and <a "
-"href=\"http://sv.gnu.org\";>Savannah</a> have shown what many free software "
-"developers who have put a codebase online already know first-hand. The vast "
-"majority of free software projects are not particularly collaborative. The "
-"median number of contributors to a free software project on SourceForge? "
-"One. A lone developer. SourceForge projects at the ninety-fifth percentile "
-"by participant size have only five contributors. More than half of these "
-"free software projects&mdash;and even most projects that have made several "
-"successful releases and been downloaded frequently, are the work of a single "
-"developer with little outside help."
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"By emphasizing the power of collaborative development and &ldquo;distributed "
-"peer review,&rdquo; open source approaches seem to have very little to say "
-"about why one should use, or contribute to, the vast majority of free "
-"software projects. Because the purported benefits of collaboration cannot be "
-"realized when there is no collaboration, the vast majority of free "
-"development projects are at no technical advantage with respect to a "
-"proprietary competitor."
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"For free software advocates, these same projects are each seen as important "
-"successes. Because every piece of free software respects its users' freedom, "
-"advocates of software freedom argue that each piece of free software begins "
-"with an inherent ethical advantage over proprietary competitors&mdash;even a "
-"more featureful one. By emphasizing freedom over practical advantages, free "
-"software's advocacy is rooted in a technical reality in a way that open "
-"source is often not. When free software is better, we can celebrate this "
-"fact. When it is not, we need not treat it as a damning critique of free "
-"software advocacy or even as a compelling argument against the use of the "
-"software in question."
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"Open source advocates must defend their thesis that freely developed "
-"software should, or will with time, be better than proprietary "
-"software. Free software supporters can instead ask, &ldquo;How can we make "
-"free software better?&rdquo; In a free software framing, high quality "
-"software exists as a means to an end rather than an end itself. Free "
-"software developers should strive to create functional, flexible software "
-"that serves its users well. But doing so is not the only way to make steps "
-"toward solving what is both an easier and a much more profoundly important "
-"goal: respecting and protecting their freedom."
-msgstr ""
-
-#. type: Content of: <p>
-msgid ""
-"Of course, we do not need to reject arguments that collaboration can play an "
-"important role in creating high-quality software. In many of the most "
-"successful free software projects, it clearly has done exactly that. The "
-"benefits of collaboration become something to understand, support, and work "
-"towards, rather than something to take for granted in the face of evidence "
-"that refuses to conform to ideology."
-msgstr ""
-
-#. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
-#. type: Content of: <div>
-msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
-msgstr ""
-
-#. type: Content of: <div><div><p>
-msgid ""
-"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>."
-msgstr ""
-
-#.  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>. 
-#. type: Content of: <div><div><p>
-msgid ""
-"Please see the <a "
-"href=\"/server/standards/README.translations.html\">Translations README</a> "
-"for information on coordinating and submitting translations of this article."
-msgstr ""
-
-#. type: Content of: <div><p>
-msgid "Copyright &copy; 1999-2011 Benjamin Mako Hill"
-msgstr ""
-
-#. type: Content of: <div><p>
-msgid ""
-"This page is licensed under a <a rel=\"license\" "
-"href=\"http://creativecommons.org/licenses/by-sa/3.0/us/\";>Creative Commons "
-"Attribution-Share Alike 3.0 United States License</a>."
-msgstr ""
-
-#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
-#. type: Content of: <div><div>
-msgid "*GNUN-SLOT: TRANSLATOR'S CREDITS*"
-msgstr ""
-
-#.  timestamp start 
-#. type: Content of: <div><p>
-msgid "Updated:"
-msgstr ""

Index: when_free_software_isnt_practically_superior.ru-en.html
===================================================================
RCS file: when_free_software_isnt_practically_superior.ru-en.html
diff -N when_free_software_isnt_practically_superior.ru-en.html
--- when_free_software_isnt_practically_superior.ru-en.html     16 Mar 2015 
15:59:39 -0000      1.1
+++ /dev/null   1 Jan 1970 00:00:00 -0000
@@ -1,187 +0,0 @@
-<!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: 1.77 -->
-<title> When Free Software Isn't (Practically) Better - GNU Project - Free 
Software Foundation</title>
-<!--#include 
virtual="/philosophy/po/when_free_software_isnt_practically_better.translist" 
-->
-<!--#include virtual="/server/banner.html" -->
-<h2> When Free Software Isn't (Practically) Better</h2>
-
-<p>The Open Source Initiative's mission statement reads, &ldquo;Open source
-is a development method for software that harnesses the power of
-distributed peer review and transparency of process. The promise of
-open source is better quality, higher reliability, more flexibility,
-lower cost, and an end to predatory vendor lock-in.&rdquo;</p>
-
-<p>For more than a decade now, the Free Software Foundation has argued
-against this &ldquo;open source&rdquo; characterization of the free software
-movement. Free software advocates have primarily argued against this
-framing because &ldquo;open source&rdquo; is an explicit effort to deemphasize
-our core message of freedom and obscure our movement's role in the
-success of the software we have built. We have argued that &ldquo;open
-source&rdquo; is bad, fundamentally, because it attempts to keep people from
-talking about software freedom. But there is another reason we should
-be wary of the open source framing. The fundamental open source
-argument, as quoted in the mission statement above, is often
-incorrect.</p>
-
-<p>Although the Open Source Initiative suggests &ldquo;the promise of open
-source is better quality, higher reliability, more flexibility,&rdquo; this
-promise is not always realized. Although we do not often advertise the
-fact, any user of an early-stage free software project can explain
-that free software is not always as convenient, in purely practical
-terms, as its proprietary competitors. Free software is sometimes low
-quality. It is sometimes unreliable. It is sometimes inflexible. If
-people take the arguments in favor of open source seriously, they must
-explain why open source has not lived up to its &ldquo;promise&rdquo; and 
conclude
-that proprietary tools would be a better choice. There is no reason we
-should have to do either.</p>
-
-<p>Richard Stallman speaks to this in his article on <a
-href="/philosophy/open-source-misses-the-point.html">Why
-Open Source Misses the Point</a> when he explains, &ldquo;The idea of open
-source is that allowing users to change and redistribute the software
-will make it more powerful and reliable. But this is not
-guaranteed. Developers of proprietary software are not necessarily
-incompetent. Sometimes they produce a program that is powerful and
-reliable, even though it does not respect the users' freedom.&rdquo;</p>
-
-<p>For open source, poor-quality software is a problem to be explained
-away or a reason to eschew the software altogether. For free software,
-it is a problem to be worked through. For free software advocates,
-glitches and missing features are never a source of shame.
-Any piece of free software that respects users' freedom has a strong
-inherent advantage over a proprietary competitor that does not. Even
-if it has other issues, free software always has freedom.</p>
-
-<p>Of course, every piece of free software must start somewhere. A brand-new
-piece of software, for example, is unlikely to be more featureful
-than an established proprietary tool. Projects
-begin with many bugs and improve over time. While open
-source advocates might argue that a project will grow into usefulness
-over time and with luck, free software projects represent important
-contributions on day one to a free software advocate. Every piece of
-software that gives users control over their technology is a step
-forward. Improved quality as a project matures is the icing on the
-cake.</p>
-
-<p>A second, perhaps even more damning, fact is that the collaborative,
-distributed, peer-review development process at the heart of the
-definition of open source bears little resemblance to the practice of
-software development in the vast majority of projects under free (or
-&ldquo;open source&rdquo;) licenses.</p>
-
-<p>Several academic studies of free software hosting sites <a
-href="http://sf.net";>SourceForge</a> and <a
-href="http://sv.gnu.org";>Savannah</a> have shown what many free
-software developers who have put a codebase online already know
-first-hand. The vast majority of free software projects are not
-particularly collaborative. The median number of contributors to a
-free software project on SourceForge?  One. A lone
-developer. SourceForge projects at the ninety-fifth percentile by
-participant size have only five contributors. More than half of these
-free software projects&mdash;and even most projects that have made several
-successful releases and been downloaded frequently, are the work of a
-single developer with little outside help.</p>
-
-<p>By emphasizing the power of collaborative development and &ldquo;distributed
-peer review,&rdquo; open source approaches seem to have very little to say
-about why one should use, or contribute to, the vast majority of free
-software projects. Because the purported benefits of collaboration
-cannot be realized when there is no collaboration, the vast majority
-of free development projects are at no technical advantage with respect to a
-proprietary competitor.</p>
-
-<p>For free software advocates, these same projects are each seen as
-important successes. Because every piece of free software respects its
-users' freedom, advocates of software freedom argue that each piece of
-free software begins with an inherent ethical advantage over
-proprietary competitors&mdash;even a more featureful one. By emphasizing
-freedom over practical advantages, free software's advocacy is rooted
-in a technical reality in a way that open source is often not. When
-free software is better, we can celebrate this fact. When it is not,
-we need not treat it as a damning critique of free software advocacy
-or even as a compelling argument against the use of the software in
-question.</p>
-
-<p>Open source advocates must defend their thesis that freely developed
-software should, or will with time, be better than proprietary
-software. Free software supporters can instead ask, &ldquo;How can we make
-free software better?&rdquo; In a free software framing, high quality software
-exists as a means to an end rather than an end itself. Free software
-developers should strive to create functional, flexible software that
-serves its users well. But doing so is not the only way to make steps
-toward solving what is both an easier and a much more profoundly
-important goal: respecting and protecting their freedom.</p>
-
-<p>Of course, we do not need to reject arguments that collaboration can
-play an important role in creating high-quality software. In many of
-the most successful free software projects, it clearly has done
-exactly that. The benefits of collaboration become something to
-understand, support, and work towards, rather than something to take
-for granted in the face of evidence that refuses to conform to
-ideology.</p>
-
-</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 3.0 US.  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; 1999-2011 Benjamin Mako Hill</p>
-
-<p>This page is licensed under a <a rel="license"
-href="http://creativecommons.org/licenses/by-sa/3.0/us/";>Creative
-Commons Attribution-Share Alike 3.0 United States License</a>.</p>
-
-<!--#include virtual="/server/bottom-notes.html" -->
-
-<p class="unprintable">Updated:
-<!-- timestamp start -->
-$Date: 2015/03/16 15:59:39 $
-<!-- timestamp end -->
-</p>
-</div>
-</div>
-</body>
-</html>
-

Index: when_free_software_isnt_practically_superior.ru.po
===================================================================
RCS file: when_free_software_isnt_practically_superior.ru.po
diff -N when_free_software_isnt_practically_superior.ru.po
--- when_free_software_isnt_practically_superior.ru.po  16 Mar 2015 15:59:38 
-0000      1.1
+++ /dev/null   1 Jan 1970 00:00:00 -0000
@@ -1,363 +0,0 @@
-# Russian translation of 
http://www.gnu.org/philosophy/when_free_software_isnt_practically_better.html
-# Copyright (C) 1999-2011 Benjamin Mako Hill
-# Copyright (C) 2013 Free Software Foundation, Inc. (translation)
-# This file is distributed under the same license as the original article.
-# Ineiev <address@hidden>, 2013
-# this translation lacks appropriate review
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: when_free_software_isnt_practically_better.html\n"
-"POT-Creation-Date: 2014-03-14 04:36+0000\n"
-"PO-Revision-Date: 2013-01-28 17:17+0000\n"
-"Last-Translator: Ineiev <address@hidden>\n"
-"Language-Team: Russian <address@hidden>\n"
-"Language: ru\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. type: Content of: <title>
-msgid ""
-"When Free Software Isn't (Practically) Better - GNU Project - Free Software "
-"Foundation"
-msgstr ""
-"Когда свободная программа (практически) 
не лучше - Проект GNU - Фонд "
-"свободного программного обеспечения"
-
-#. type: Content of: <h2>
-msgid "When Free Software Isn't (Practically) Better"
-msgstr "Когда свободная программа 
(практически) не лучше"
-
-#. type: Content of: <p>
-msgid ""
-"The Open Source Initiative's mission statement reads, &ldquo;Open source is "
-"a development method for software that harnesses the power of distributed "
-"peer review and transparency of process. The promise of open source is "
-"better quality, higher reliability, more flexibility, lower cost, and an end "
-"to predatory vendor lock-in.&rdquo;"
-msgstr ""
-"Заявление о задачах Инициативы открытого 
исходного текста гласит: &ldquo;"
-"Открытый исходный текст&nbsp;&mdash; метод 
разработки программ, который "
-"обуздывает энергию распределенных 
взаимных проверок и прозрачности процесса. 
"
-"Открытый исходный текст обещает лучшее 
качество, повышенную надежность "
-"и&nbsp;гибкость, более низкую стоимость 
и&nbsp;конец хищнического замыкания "
-"на&nbsp;производителе&rdquo;."
-
-#. type: Content of: <p>
-msgid ""
-"For more than a decade now, the Free Software Foundation has argued against "
-"this &ldquo;open source&rdquo; characterization of the free software "
-"movement. Free software advocates have primarily argued against this framing "
-"because &ldquo;open source&rdquo; is an explicit effort to deemphasize our "
-"core message of freedom and obscure our movement's role in the success of "
-"the software we have built. We have argued that &ldquo;open source&rdquo; is "
-"bad, fundamentally, because it attempts to keep people from talking about "
-"software freedom. But there is another reason we should be wary of the open "
-"source framing. The fundamental open source argument, as quoted in the "
-"mission statement above, is often incorrect."
-msgstr ""
-"Уже более десятилетия Фонд свободного 
программного обеспечения оспаривает "
-"это описание движения за свободное 
программное обеспечения с точки зрения "
-"&ldquo;открытого исходного текста&rdquo;. 
Сторонники свободного программного "
-"обеспечения возражали против такой 
формулировки прежде всего потому, что "
-"&ldquo;открытый исходный текст&rdquo;&nbsp;&mdash; 
это явная попытка "
-"затушевать наше центральное сообщение о 
свободе и затенить роль нашего "
-"движения в успехе того корпуса программ, 
который мы построили. Мы поясняли, "
-"что выражение &ldquo;открытый исходный 
текст&rdquo; плохо в принципе, потому "
-"что оно пытается удержать людей от 
разговоров о свободе программ. Но есть и "
-"другая причина, по которой нам следует 
опасаться формулировок открытого "
-"исходного текста. Основополагающий 
аргумент открытого исходного текста, "
-"процитированный выше из заявления о 
задачах, часто неверен."
-
-#. type: Content of: <p>
-msgid ""
-"Although the Open Source Initiative suggests &ldquo;the promise of open "
-"source is better quality, higher reliability, more flexibility,&rdquo; this "
-"promise is not always realized. Although we do not often advertise the fact, "
-"any user of an early-stage free software project can explain that free "
-"software is not always as convenient, in purely practical terms, as its "
-"proprietary competitors. Free software is sometimes low quality. It is "
-"sometimes unreliable. It is sometimes inflexible. If people take the "
-"arguments in favor of open source seriously, they must explain why open "
-"source has not lived up to its &ldquo;promise&rdquo; and conclude that "
-"proprietary tools would be a better choice. There is no reason we should "
-"have to do either."
-msgstr ""
-"Хотя Инициатива открытого исходного 
текста предполагает, что &ldquo;открытый "
-"исходный текст обещает лучшее качество, 
повышенную надежность и&nbsp;"
-"гибкость&rdquo;, это обещание не всегда 
реализуется. Хотя мы не часто "
-"обращаем внимание на этот факт, любой 
пользователь проекта по созданию "
-"свободных программ, находящегося в ранней 
стадии, скажет вам, что свободные "
-"программы не всегда так же удобны, с чисто 
практической точки зрения, как их "
-"несвободные конкуренты. Качество 
свободных программ иногда низко. Иногда 
они "
-"ненадежны. Иногда они негибки. Если люди 
серьезно относятся к аргументам в "
-"пользу открытого исходного текста, они 
должны объяснить, почему открытый "
-"исходный текст не выполнил своего 
&ldquo;обещания&rdquo; и сделать вывод, "
-"что несвободные средства были бы лучшим 
выбором. Нам не нужно делать ни "
-"того, ни другого."
-
-#. type: Content of: <p>
-msgid ""
-"Richard Stallman speaks to this in his article on <a href=\"/philosophy/open-"
-"source-misses-the-point.html\">Why Open Source Misses the Point</a> when he "
-"explains, &ldquo;The idea of open source is that allowing users to change "
-"and redistribute the software will make it more powerful and reliable. But "
-"this is not guaranteed. Developers of proprietary software are not "
-"necessarily incompetent. Sometimes they produce a program that is powerful "
-"and reliable, even though it does not respect the users' freedom.&rdquo;"
-msgstr ""
-"Ричард Столмен говорит об этом в своей 
статье &ldquo;<a href=\"/philosophy/"
-"open-source-misses-the-point.html\">Почему открытый исх
одный текст не "
-"передает понятия &lsquo;свободная 
программа&rsquo;</a>&rdquo;, когда он "
-"поясняет: &ldquo;Идея открытого исходного 
текста состоит в том, что "
-"разрешение пользователям изменять и 
распространять программы сделает их "
-"эффективнее и надежнее. Но это не 
гарантировано. Разработчики несвободных "
-"программ не обязательно некомпетентны. 
Иногда они выпускают программу, "
-"которая эффективна и надежна, хотя она и 
не уважает свободу "
-"пользователей&rdquo;."
-
-#. type: Content of: <p>
-msgid ""
-"For open source, poor-quality software is a problem to be explained away or "
-"a reason to eschew the software altogether. For free software, it is a "
-"problem to be worked through. For free software advocates, glitches and "
-"missing features are never a source of shame.  Any piece of free software "
-"that respects users' freedom has a strong inherent advantage over a "
-"proprietary competitor that does not. Even if it has other issues, free "
-"software always has freedom."
-msgstr ""
-"Для открытого исходного текста 
низкокачественные программы&nbsp;&mdash; "
-"проблема, которую следует разъяснить, или 
причина сторониться этих программ "
-"вообще. Для свободных программ это 
проблема, над которой следует работать. "
-"Для сторонников свободного программного 
обеспечения прорехи и недостающие "
-"возможности никогда не станут причиной 
для стыда. У любой свободной "
-"программы, уважающей свободу 
пользователей, есть сильное и неотъемлемое 
"
-"преимущество перед несвободным 
конкурентом, который свободу 
пользователей не "
-"уважает. Даже если у свободной программы 
нет чего-то еще, у нее всегда есть "
-"свобода."
-
-#. type: Content of: <p>
-msgid ""
-"Of course, every piece of free software must start somewhere. A brand-new "
-"piece of software, for example, is unlikely to be more featureful than an "
-"established proprietary tool. Projects begin with many bugs and improve over "
-"time. While open source advocates might argue that a project will grow into "
-"usefulness over time and with luck, free software projects represent "
-"important contributions on day one to a free software advocate. Every piece "
-"of software that gives users control over their technology is a step "
-"forward. Improved quality as a project matures is the icing on the cake."
-msgstr ""
-"Конечно, каждая свободная программа 
должна с чего-то начинаться. Например, "
-"только что возникшая свободная программа 
едва ли будет более богата "
-"функциями, чем развитый несвободный 
пакет. Проекты начинаются с большого "
-"количества ошибок и улучшаются со 
временем. В то время как сторонники "
-"открытого исходного текста могли бы 
убеждать, что со временем и при "
-"известной доле везения проект вырастет до 
полезного, для сторонника "
-"свободных программ проекты по созданию 
свободных программ представляют собой "
-"важный вклад с первого же дня. Любая 
программа, которая дает пользователям "
-"контроль над их техникой&nbsp;&mdash; это шаг 
вперед. Повышенное качество "
-"при достижении проектом зрелости&nbsp;&mdash; 
это масло на куске хлеба."
-
-#. type: Content of: <p>
-msgid ""
-"A second, perhaps even more damning, fact is that the collaborative, "
-"distributed, peer-review development process at the heart of the definition "
-"of open source bears little resemblance to the practice of software "
-"development in the vast majority of projects under free (or &ldquo;open "
-"source&rdquo;) licenses."
-msgstr ""
-"Второй, возможно, еще более вопиющий факт 
заключается в том, что "
-"распределенный процесс разработки с 
сотрудничеством и взаимной проверкой, "
-"который составляет сердце определения 
открытого исходного текста, имеет мало "
-"общего с практикой разработки программ в 
подавляющем большинстве проектов "
-"под лицензиями свободных программ (или 
программ &ldquo;с открытым исходным "
-"текстом&rdquo;)."
-
-#. type: Content of: <p>
-msgid ""
-"Several academic studies of free software hosting sites <a href=\"http://sf.";
-"net\">SourceForge</a> and <a href=\"http://sv.gnu.org\";>Savannah</a> have "
-"shown what many free software developers who have put a codebase online "
-"already know first-hand. The vast majority of free software projects are not "
-"particularly collaborative. The median number of contributors to a free "
-"software project on SourceForge? One. A lone developer. SourceForge projects "
-"at the ninety-fifth percentile by participant size have only five "
-"contributors. More than half of these free software projects&mdash;and even "
-"most projects that have made several successful releases and been downloaded "
-"frequently, are the work of a single developer with little outside help."
-msgstr ""
-"Несколько научных исследований сайтов <a 
href=\"http://sf.net\";>SourceForge</"
-"a> и <a href=\"http://sv.gnu.org\";>Savannah</a>, 
предоставляющих "
-"инфраструктуру для разработки свободных 
программ, показали то, что многие "
-"разработчики свободных программ, которым 
доводилось размещать тексты "
-"программ в Интернете, уже знают по 
собственному опыту. Подавляющее "
-"большинство проектов по разработке 
свободных программ не слишком склонно к "
-"сотрудничеству. Какова медиана 
соразработчиков проекта по созданию 
свободных "
-"программ на SourceForge? Один. Одинокий 
разработчик. В девяноста пяти "
-"процентах проектов SourceForge участвует не 
более пяти соразработчиков. "
-"Более половины из этих проектов по 
созданию свободных программ&nbsp;&mdash; "
-"и даже большинство проектов, которые 
сделали несколько успешных выпусков и "
-"файлы которых часто запрашивались по 
сети&nbsp;&mdash; представляют собой "
-"работу единственного разработчика 
практически без помощи со стороны."
-
-#. type: Content of: <p>
-msgid ""
-"By emphasizing the power of collaborative development and &ldquo;distributed "
-"peer review,&rdquo; open source approaches seem to have very little to say "
-"about why one should use, or contribute to, the vast majority of free "
-"software projects. Because the purported benefits of collaboration cannot be "
-"realized when there is no collaboration, the vast majority of free "
-"development projects are at no technical advantage with respect to a "
-"proprietary competitor."
-msgstr ""
-"Подчеркивая эффективность совместной 
разработки и &ldquo;распределенных "
-"взаимных проверок&rdquo;, подходы открытого 
исходного текста, кажется, почти "
-"ничего не говорят о том, почему кому-то 
следует делать вклад в подавляющее "
-"большинство проектов по разработке 
свободных программ или пользоваться ими. "
-"Поскольку предполагаемые выгоды от 
сотрудничества не могут быть реализованы, "
-"когда никакого сотрудничества нет, 
подавляющее большинство проектов по "
-"разработке свободных программ не имеют 
никаких технических преимуществ по "
-"сравнению с несвободным конкурентом."
-
-#. type: Content of: <p>
-msgid ""
-"For free software advocates, these same projects are each seen as important "
-"successes. Because every piece of free software respects its users' freedom, "
-"advocates of software freedom argue that each piece of free software begins "
-"with an inherent ethical advantage over proprietary competitors&mdash;even a "
-"more featureful one. By emphasizing freedom over practical advantages, free "
-"software's advocacy is rooted in a technical reality in a way that open "
-"source is often not. When free software is better, we can celebrate this "
-"fact. When it is not, we need not treat it as a damning critique of free "
-"software advocacy or even as a compelling argument against the use of the "
-"software in question."
-msgstr ""
-"Сторонниками свободного программного 
обеспечения эти же самые проекты "
-"рассматриваются как важные достижения. 
Поскольку каждая свободная программа "
-"уважает свободу своих пользователей, 
защитники свободы программ утверждают, "
-"что каждая свободная программа рождается 
с неотъемлемым этическим "
-"преимуществом перед несвободными 
конкурентами&nbsp;&mdash; даже если те "
-"более богаты возможностями. Выводя на 
первое место свободу, а не "
-"практические достоинства, аргументация 
свободного программного обеспечения "
-"уходит корнями в реалии техники так, как 
открытый исходный текст часто этого "
-"не делает. Когда свободные программы 
лучше, мы можем отметить этот факт. "
-"Когда нет, нам нет нужды относиться к 
этому как к неотразимой критике "
-"аргументации свободного программного 
обеспечения или даже как к "
-"убедительному аргументу против 
применения данной программы."
-
-#. type: Content of: <p>
-msgid ""
-"Open source advocates must defend their thesis that freely developed "
-"software should, or will with time, be better than proprietary software. "
-"Free software supporters can instead ask, &ldquo;How can we make free "
-"software better?&rdquo; In a free software framing, high quality software "
-"exists as a means to an end rather than an end itself. Free software "
-"developers should strive to create functional, flexible software that serves "
-"its users well. But doing so is not the only way to make steps toward "
-"solving what is both an easier and a much more profoundly important goal: "
-"respecting and protecting their freedom."
-msgstr ""
-"Сторонники открытого исходного текста 
должны защищать свой тезис о том, что "
-"свободно разрабатываемые программы 
должны стать или станут со временем "
-"лучше, чем несвободные. Сторонники 
свободных программ вместо этого могут "
-"спрашивать: &ldquo;Как сделать свободные 
программы лучше?&rdquo; В контексте "
-"свободного программного обеспечения 
высокое качество программ существует как "
-"средство к достижению цели, а не как 
самоцель. Разработчикам свободных "
-"программ следует стремиться к созданию 
богатых, гибких программ, которые "
-"хорошо служат пользователям. Но это не 
единственный способ предпринять шаги "
-"к достижению того, что является и более 
легкой, и гораздо более глубокой и "
-"важной целью: уважение и защита их 
свободы."
-
-#. type: Content of: <p>
-msgid ""
-"Of course, we do not need to reject arguments that collaboration can play an "
-"important role in creating high-quality software. In many of the most "
-"successful free software projects, it clearly has done exactly that. The "
-"benefits of collaboration become something to understand, support, and work "
-"towards, rather than something to take for granted in the face of evidence "
-"that refuses to conform to ideology."
-msgstr ""
-"Конечно, нам не нужно отвергать 
аргументов о том, что сотрудничество может "
-"играть важную роль в создании программ 
высокого качества. Ясно, что во "
-"многих из самых успешных проектов по 
созданию свободных программ их именно "
-"так и делали. Выгоды сотрудничества 
становятся тем, что нужно понимать, "
-"поддерживать, над чем нужно работать, а не 
тем, что нужно принимать как само "
-"собой разумеющееся перед лицом 
свидетельств, которые отказываются 
следовать "
-"идеологии."
-
-# type: Content of: <div><div>
-#. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
-#. type: Content of: <div>
-msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
-msgstr " "
-
-#. type: Content of: <div><div><p>
-msgid ""
-"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"
-"org&gt;</a>."
-msgstr ""
-"Пожалуйста, присылайте общие запросы 
фонду и GNU по адресу <a href=\"mailto:";
-"address@hidden">&lt;address@hidden&gt;</a>. Есть также <a 
href=\"/contact/"
-"\">другие способы связаться</a> с фондом. 
Отчеты о неработающих ссылках и "
-"другие поправки или предложения можно 
присылать по адресу <a href=\"mailto:";
-"address@hidden">&lt;address@hidden&gt;</a>."
-
-#.  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>. 
-#. type: Content of: <div><div><p>
-msgid ""
-"Please see the <a href=\"/server/standards/README.translations.html"
-"\">Translations README</a> for information on coordinating and submitting "
-"translations of this article."
-msgstr ""
-"Мы старались сделать этот перевод точным 
и качественным, но исключить "
-"возможность ошибки мы не можем. 
Присылайте, пожалуйста, свои замечания и "
-"предложения по переводу по адресу <a 
href=\"mailto:address@hidden";
-"\">&lt;address@hidden&gt;</a>. </p><p>Сведения по 
координации и "
-"предложениям переводов наших статей см. в 
<a href=\"/server/standards/README."
-"translations.html\">&ldquo;Руководстве по 
переводам&rdquo;</a>."
-
-#. type: Content of: <div><p>
-msgid "Copyright &copy; 1999-2011 Benjamin Mako Hill"
-msgstr ""
-"Copyright &copy; 1999-2011 Benjamin Mako Hill<br />Copyright &copy; 2013 "
-"Free Software Foundation, Inc. (translation)"
-
-#. type: Content of: <div><p>
-msgid ""
-"This page is licensed under a <a rel=\"license\" href=\"http://";
-"creativecommons.org/licenses/by-sa/3.0/us/\">Creative Commons Attribution-"
-"Share Alike 3.0 United States License</a>."
-msgstr ""
-"Это произведение доступно по <a rel=\"license\" 
href=\"http://";
-"creativecommons.org/licenses/by-sa/3.0/us/deed.ru\">лицензии Creative 
"
-"Commons Attribution-NoDerivs (<em>Атрибуция&nbsp;&mdash; С сох
ранением "
-"условий</em>) 3.0 США</a>."
-
-# type: Content of: <div><div>
-#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
-#. type: Content of: <div><div>
-msgid "*GNUN-SLOT: TRANSLATOR'S CREDITS*"
-msgstr ""
-"<em>Внимание! В подготовке этого перевода 
участвовал только один человек. Вы "
-"можете существенно улучшить перевод, если 
проверите его и расскажете о "
-"найденных ошибках в <a 
href=\"http://savannah.gnu.org/projects/www-ru";
-"\">русской группе переводов gnu.org</a>.</em>"
-
-#.  timestamp start 
-#. type: Content of: <div><p>
-msgid "Updated:"
-msgstr "Обновлено:"

Index: when_free_software_isnt_practically_superior.translist
===================================================================
RCS file: when_free_software_isnt_practically_superior.translist
diff -N when_free_software_isnt_practically_superior.translist
--- when_free_software_isnt_practically_superior.translist      16 Mar 2015 
15:59:39 -0000      1.1
+++ /dev/null   1 Jan 1970 00:00:00 -0000
@@ -1,15 +0,0 @@
-<!-- begin translist file -->
-<!--#set var="TRANSLATION_LIST"
-value='<div id="translations">
-<p>
-<span dir="ltr" class="original"><a lang="en" hreflang="en" 
href="/philosophy/when_free_software_isnt_practically_better.en.html">English</a>&nbsp;[en]</span>&nbsp;&nbsp;
-<span dir="ltr"><a lang="fr" hreflang="fr" 
href="/philosophy/when_free_software_isnt_practically_better.fr.html">français</a>&nbsp;[fr]</span>&nbsp;&nbsp;
-<span dir="ltr"><a lang="ru" hreflang="ru" 
href="/philosophy/when_free_software_isnt_practically_better.ru.html">русский</a>&nbsp;[ru]</span>&nbsp;&nbsp;
-</p>
-</div>' -->
-<!--#if expr="$HTML_BODY = yes" -->
-<!-- Fallback for old position of translist; to be removed
-     when translists in all translations are included before banner.html. -->
-<!--#echo encoding="none" var="TRANSLATION_LIST" -->
-<!--#endif -->
-<!-- end translist file -->



reply via email to

[Prev in Thread] Current Thread [Next in Thread]