[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www gnu/po/why-programs-should-be-shared.tr.po ...
From: |
GNUN |
Subject: |
www gnu/po/why-programs-should-be-shared.tr.po ... |
Date: |
Thu, 9 Apr 2020 11:29:25 -0400 (EDT) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 20/04/09 11:29:25
Modified files:
gnu/po : why-programs-should-be-shared.tr.po
licenses/po : fdl-howto.tr.po
Added files:
gnu : why-programs-should-be-shared.tr.html
gnu/po : why-programs-should-be-shared.tr-en.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/why-programs-should-be-shared.tr.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/why-programs-should-be-shared.tr.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/why-programs-should-be-shared.tr-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/fdl-howto.tr.po?cvsroot=www&r1=1.1&r2=1.2
Patches:
Index: gnu/po/why-programs-should-be-shared.tr.po
===================================================================
RCS file: /web/www/www/gnu/po/why-programs-should-be-shared.tr.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- gnu/po/why-programs-should-be-shared.tr.po 9 Apr 2020 15:20:19 -0000
1.1
+++ gnu/po/why-programs-should-be-shared.tr.po 9 Apr 2020 15:29:25 -0000
1.2
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: why-programs-should-be-shared.html\n"
-"POT-Creation-Date: 2020-03-30 14:07+0300\n"
+"POT-Creation-Date: 2016-11-18 06:57+0000\n"
"PO-Revision-Date: 2020-04-05 17:28+0200\n"
"Last-Translator: T. E. Kalayci <address@hidden>\n"
"Language-Team: Turkish <address@hidden>\n"
Index: licenses/po/fdl-howto.tr.po
===================================================================
RCS file: /web/www/www/licenses/po/fdl-howto.tr.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- licenses/po/fdl-howto.tr.po 9 Apr 2020 15:20:20 -0000 1.1
+++ licenses/po/fdl-howto.tr.po 9 Apr 2020 15:29:25 -0000 1.2
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: fdl-howto.html\n"
-"POT-Creation-Date: 2020-04-06 20:22+0300\n"
+"POT-Creation-Date: 2014-04-05 00:01+0000\n"
"PO-Revision-Date: 2020-04-09 17:08+0200\n"
"Last-Translator: T. E. Kalayci <address@hidden>\n"
"Language-Team: Turkish <address@hidden>\n"
@@ -17,7 +17,6 @@
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Poedit 2.3\n"
-
#. type: Content of: <title>
msgid "Tips on Using the GNU FDL - GNU Project - Free Software Foundation"
msgstr ""
Index: gnu/why-programs-should-be-shared.tr.html
===================================================================
RCS file: gnu/why-programs-should-be-shared.tr.html
diff -N gnu/why-programs-should-be-shared.tr.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gnu/why-programs-should-be-shared.tr.html 9 Apr 2020 15:29:25 -0000
1.1
@@ -0,0 +1,155 @@
+<!--#set var="ENGLISH_PAGE" value="/gnu/why-programs-should-be-shared.en.html"
-->
+
+<!--#include virtual="/server/header.tr.html" -->
+<!-- Parent-Version: 1.79 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Programlar neden paylaÅılmalıdır - GNU Projesi - Ãzgür Yazılım
Vakfı</title>
+
+<!--#include virtual="/gnu/po/why-programs-should-be-shared.translist" -->
+<!--#include virtual="/server/banner.tr.html" -->
+<h2>Programlar neden paylaÅılmalıdır</h2>
+
+<p><strong>yazan <a href="http://www.stallman.org/">Richard
+Stallman</a></strong></p>
+
+ <blockquote>
+ <p>Mayıs 1983 tarihli bir dosyada bulunan bu metni Richard Stallman
yazdı,
+ancak daha önce mi yoksa daha sonra mı yazıldıÄı belli deÄil. Mayıs
1983'te
+özgür bir iÅletim sistemi geliÅtirme planlarını kendi kendine
düÅünüyordu,
+ancak MIT Lisp Makinesi gibi bir Åeyden ziyade Unix benzeri bir sistem
+yapmaya henüz karar vermemiÅti.</p>
+
+ <p>"Free" kelimesinin iki anlamı olan ücretsiz ve özgürü henüz
kavramsal olarak
+ayırt etmemiÅti; mesaj bedelsiz kopyalar bakımından ifade edilmiÅti, ancak
+siz yine de bunun ayrıca kullanıcıların özgürlüÄe sahip olduÄu
anlamına
+geldiÄini kabul edin.</p>
+ </blockquote>
+
+<p>BeŠyıl önce SAIL, MIT, CMU, vb. yerlerde yazılan yararlı herhangi bir
+programın paylaÅılabileceÄine kesin gözüyle bakılırdı. O zamandan
beri, bu
+üniversiteler tıpkı yazılım evleri gibi davranmaya baÅladı; yararlı
olan her
+Åey aÅırı pahalı satılacaktı (genellikle hükümet harcamalarıyla
yazıldıktan
+sonra).</p>
+
+<p>Ä°nsanlar, yazılım hediye etmenin neden zararlı olduÄuna iliÅkin her
türlü
+mazereti bulurlar. Bu sözde sorunlar, biz paylaÅmak <em>istediÄimizde</em>
+bizi asla rahatsız etmedi ve EMACS'i etkilemedi, bu yüzden bu sorunların
+düzmece olduÄundan kuÅkulanıyorum.</p>
+
+<p>ÃrneÄin, insanlar Åirketlerin onu “çalacaÄını” ve
satacaÄını
+söylüyorlar. EÄer öyleyse, Stanford'un onu satmasından daha kötü
olamaz! En
+azından insanlar ücretsiz bir kopya alma seçeneÄine sahip
+olurlardı. Kullanıcılar bakımı yapılan bir yazılım mı satın almak
istiyor? O
+zaman insanların hizmet sözleÅmeleri satmasına izin verin, ancak
yazılımın
+kendisini özgür bırakın.</p>
+
+<p>Sanırım yazılımı paylaÅmamak için var olabileceÄini
düÅündüÄünüz herhangi
+bir gerekçeyi bertaraf edebilirim. Ancak daha önemli olan, neden
paylaÅmamız
+<em>gerektiÄidir</em>:</p>
+
+<p>Yapay engeller aÅılırsa, aynı miktarda çabayla daha fazla iÅ
yaparız. Ve
+kendimizi diÄer herkesle daha uyumlu hissederiz.</p>
+
+<p>Yazılım paylaÅımı, bilgisayar bilimi alanında bilimsel iÅbirliÄinin
aldıÄı
+biçimdir. Ãniversiteler bilimsel iÅbirliÄi ilkesini savunurlardı. Bu
ilkeden
+kâr için vazgeçmeleri doÄru mudur?</p>
+
+<p>Onlara izin vermeli miyiz?</p>
+
+<p>Åu anda buradaki üniversite mezunu öÄrenciler, özellikle satıÅa
yönelik
+programlama projeleri üzerinde çalıÅıyorlar. Fakat beÅ yıl önce
olduÄu gibi
+bir düÅünce ortamı oluÅturursak, üniversite bunu yapmaya cesaret edemez.
Ve
+paylaÅmaya baÅladıÄınızda, baÅkaları da sizinle paylaÅmaya
baÅlayabilir.</p>
+
+<p>Ä°Åte bu nedenle hemen Åimdi paylaÅmaya tekrar baÅlayalım.</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.tr.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Lütfen FSF ve GNU ile ilgili sorularınızı <a
+href="mailto:address@hidden"><address@hidden></a> adresine iletin. FSF
ile
+iletiÅim kurmanın <a href="/contact/">baÅka yolları</a> da vardır. Lütfen
+çalıÅmayan baÄlantıları ve baÅka düzeltmeleri veya önerilerinizi <a
+href="mailto:address@hidden"><address@hidden></a> adresine
+gönderin.</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">
+
+ <address@hidden></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>. -->
+Ãevirilerimizde bulmuÅ olabileceÄiniz hataları, aklınızdaki soru ve
+önerilerinizi lütfen <a
+href="mailto:address@hidden">bize bildirin</a>.</p><p>Bu
+yazının çeviri düzenlemesi ve sunuÅu ile ilgili bilgi için lütfen <a
+href="/server/standards/README.translations.html">Ãeviriler BENÄ°OKU</a>
+sayfasına bakın. Bu sayfanın ve diÄer tüm sayfaların Türkçe çevirileri
+gönüllüler tarafından yapılmaktadır; Türkçe niteliÄi yüksek bir <a
+href="/home.html">www.gnu.org</a> için bize yardımcı olmak istiyorsanız, <a
+href="https://savannah.gnu.org/projects/www-tr">çalıÅma sayfamızı</a>
+ziyaret edebilirsiniz.</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 © 2015, 2016 Free Software Foundation, Inc.</p>
+
+<p>Bu sayfa <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/deed.tr">Creative
+Commons Alıntı-Türetilemez 4.0 Uluslararası Lisansı</a> altında
+lisanslanmıÅtır.</p>
+
+<!--#include virtual="/server/bottom-notes.tr.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<p><strong>Ãeviriye katkıda bulunanlar:</strong></p>
+<ul>
+<li>Mert Gör <a
+href="mailto:address@hidden"><address@hidden></a>, 2020</li>
+</ul></div>
+
+<p class="unprintable"><!-- timestamp start -->
+Son Güncelleme:
+
+$Date: 2020/04/09 15:29:25 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
Index: gnu/po/why-programs-should-be-shared.tr-en.html
===================================================================
RCS file: gnu/po/why-programs-should-be-shared.tr-en.html
diff -N gnu/po/why-programs-should-be-shared.tr-en.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gnu/po/why-programs-should-be-shared.tr-en.html 9 Apr 2020 15:29:25
-0000 1.1
@@ -0,0 +1,126 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.79 -->
+<title>Why Programs Should be Shared
+- GNU Project - Free Software Foundation</title>
+ <!--#include virtual="/gnu/po/why-programs-should-be-shared.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Why Programs Should be Shared</h2>
+
+<p><strong>by <a href="http://www.stallman.org/">Richard
Stallman</a></strong></p>
+
+ <blockquote>
+ <p>Richard Stallman wrote this text, which was found in a file dated May
+ 1983, though it is not clear whether it was written then or earlier.
+ In May 1983 he was privately considering plans to develop a
+ free operating system, but he may not yet have decided to make it a
+ Unix-like system rather than something like the MIT Lisp Machine.</p>
+
+ <p>He had not yet conceptually distinguished the two meanings of
+ “free;” this message is formulated in terms of gratis
+ copies, but take for granted that this means users also have freedom.</p>
+ </blockquote>
+
+<p>Five years ago one could take for granted that any useful program
+written at SAIL, MIT, CMU, etc. would be shared. Since then, these
+universities have started acting just like software houses—everything
+useful will be sold for an arm and a leg (usually after being written
+at gov't expense).</p>
+
+<p>People find all sorts of excuses why it's harmful to give away
+software. These supposed problems never bothered us back when we
+<em>wanted</em> to share, and haven't affected EMACS, so I suspect they are
+bogus.</p>
+
+<p>For example, people say that companies will “steal” it
+and sell it. If so, that would be no worse than Stanford selling it!
+At least people would have the choice of getting a free copy. Users
+want to buy maintained software? Then let people sell service
+contracts—but give the software itself free.</p>
+
+<p>I think I can dispose of any reasons you may think exist
+for not sharing software. But more important is the reason
+why we <em>should</em> share:</p>
+
+<p>We would get more done with the same amount of work, if
+artificial obstacles were removed. And we would feel
+more in harmony with everyone else.</p>
+
+<p>Sharing software is the form that scientific cooperation
+takes in the field of computer science. Universities used
+to defend the principle of scientific cooperation.
+Is it right for them to throw it over for profit?</p>
+
+<p>Should we let them?</p>
+
+<p>Right now graduate students here are working on programming
+projects that are specifically intended for sale. But if
+we create a climate of opinion like that of five years ago,
+the university wouldn't dare to do this. And if you start
+sharing, other people might start sharing with you.</p>
+
+<p>So let's start sharing again.</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 & GNU inquiries to
+<a href="mailto:address@hidden"><address@hidden></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"><address@hidden></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">
+ <address@hidden></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 © 2015, 2016 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: 2020/04/09 15:29:25 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>