[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www gnu/po/why-programs-should-be-shared.transl...
From: |
GNUN |
Subject: |
www gnu/po/why-programs-should-be-shared.transl... |
Date: |
Thu, 9 Apr 2020 11:59:12 -0400 (EDT) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 20/04/09 11:59:12
Modified files:
gnu/po : why-programs-should-be-shared.translist
licenses/po : fdl-howto.tr.po fdl-howto.translist
Added files:
licenses : fdl-howto.tr.html
licenses/po : fdl-howto.tr-en.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/why-programs-should-be-shared.translist?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/fdl-howto.tr.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/fdl-howto.tr.po?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/fdl-howto.translist?cvsroot=www&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/fdl-howto.tr-en.html?cvsroot=www&rev=1.1
Patches:
Index: gnu/po/why-programs-should-be-shared.translist
===================================================================
RCS file: /web/www/www/gnu/po/why-programs-should-be-shared.translist,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- gnu/po/why-programs-should-be-shared.translist 15 Mar 2020 18:34:42
-0000 1.10
+++ gnu/po/why-programs-should-be-shared.translist 9 Apr 2020 15:59:12
-0000 1.11
@@ -9,6 +9,7 @@
<span dir="ltr">[nl] <a lang="nl" hreflang="nl"
href="/gnu/why-programs-should-be-shared.nl.html">Nederlands</a> </span>
<span dir="ltr">[pt-br] <a lang="pt-br" hreflang="pt-br"
href="/gnu/why-programs-should-be-shared.pt-br.html">português</a>
</span>
<span dir="ltr">[ru] <a lang="ru" hreflang="ru"
href="/gnu/why-programs-should-be-shared.ru.html">ÑÑÑÑкий</a>
</span>
+<span dir="ltr">[tr] <a lang="tr" hreflang="tr"
href="/gnu/why-programs-should-be-shared.tr.html">Türkçe</a> </span>
<span dir="ltr">[uk] <a lang="uk" hreflang="uk"
href="/gnu/why-programs-should-be-shared.uk.html">ÑкÑаÑнÑÑка</a>
</span>
<span dir="ltr">[zh-cn] <a lang="zh-cn" hreflang="zh-cn"
href="/gnu/why-programs-should-be-shared.zh-cn.html">ç®ä½ä¸æ</a>
</span>
</p>
@@ -21,6 +22,7 @@
<link rel="alternate" type="text/html" lang="nl" hreflang="nl"
href="/gnu/why-programs-should-be-shared.nl.html" title="Nederlands" />
<link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br"
href="/gnu/why-programs-should-be-shared.pt-br.html" title="português" />
<link rel="alternate" type="text/html" lang="ru" hreflang="ru"
href="/gnu/why-programs-should-be-shared.ru.html" title="ÑÑÑÑкий" />
+<link rel="alternate" type="text/html" lang="tr" hreflang="tr"
href="/gnu/why-programs-should-be-shared.tr.html" title="Türkçe" />
<link rel="alternate" type="text/html" lang="uk" hreflang="uk"
href="/gnu/why-programs-should-be-shared.uk.html" title="ÑкÑаÑнÑÑка"
/>
<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn"
href="/gnu/why-programs-should-be-shared.zh-cn.html" title="ç®ä½ä¸æ" />
<!-- end translist file -->
Index: licenses/po/fdl-howto.tr.po
===================================================================
RCS file: /web/www/www/licenses/po/fdl-howto.tr.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- licenses/po/fdl-howto.tr.po 9 Apr 2020 15:38:39 -0000 1.3
+++ licenses/po/fdl-howto.tr.po 9 Apr 2020 15:59:12 -0000 1.4
@@ -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:36+0200\n"
"Last-Translator: T. E. Kalayci <address@hidden>\n"
"Language-Team: Turkish <address@hidden>\n"
Index: licenses/po/fdl-howto.translist
===================================================================
RCS file: /web/www/www/licenses/po/fdl-howto.translist,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- licenses/po/fdl-howto.translist 15 Mar 2020 17:29:08 -0000 1.18
+++ licenses/po/fdl-howto.translist 9 Apr 2020 15:59:12 -0000 1.19
@@ -10,6 +10,7 @@
<span dir="ltr">[pl] <a lang="pl" hreflang="pl"
href="/licenses/fdl-howto.pl.html">polski</a> </span>
<span dir="ltr">[pt-br] <a lang="pt-br" hreflang="pt-br"
href="/licenses/fdl-howto.pt-br.html">português</a> </span>
<span dir="ltr">[ru] <a lang="ru" hreflang="ru"
href="/licenses/fdl-howto.ru.html">ÑÑÑÑкий</a> </span>
+<span dir="ltr">[tr] <a lang="tr" hreflang="tr"
href="/licenses/fdl-howto.tr.html">Türkçe</a> </span>
<span dir="ltr">[uk] <a lang="uk" hreflang="uk"
href="/licenses/fdl-howto.uk.html">ÑкÑаÑнÑÑка</a> </span>
<span dir="ltr">[zh-cn] <a lang="zh-cn" hreflang="zh-cn"
href="/licenses/fdl-howto.zh-cn.html">ç®ä½ä¸æ</a> </span>
<span dir="ltr">[zh-tw] <a lang="zh-tw" hreflang="zh-tw"
href="/licenses/fdl-howto.zh-tw.html">ç¹é«ä¸æ</a> </span>
@@ -24,6 +25,7 @@
<link rel="alternate" type="text/html" lang="pl" hreflang="pl"
href="/licenses/fdl-howto.pl.html" title="polski" />
<link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br"
href="/licenses/fdl-howto.pt-br.html" title="português" />
<link rel="alternate" type="text/html" lang="ru" hreflang="ru"
href="/licenses/fdl-howto.ru.html" title="ÑÑÑÑкий" />
+<link rel="alternate" type="text/html" lang="tr" hreflang="tr"
href="/licenses/fdl-howto.tr.html" title="Türkçe" />
<link rel="alternate" type="text/html" lang="uk" hreflang="uk"
href="/licenses/fdl-howto.uk.html" title="ÑкÑаÑнÑÑка" />
<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn"
href="/licenses/fdl-howto.zh-cn.html" title="ç®ä½ä¸æ" />
<link rel="alternate" type="text/html" lang="zh-tw" hreflang="zh-tw"
href="/licenses/fdl-howto.zh-tw.html" title="ç¹é«ä¸æ" />
Index: licenses/fdl-howto.tr.html
===================================================================
RCS file: licenses/fdl-howto.tr.html
diff -N licenses/fdl-howto.tr.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ licenses/fdl-howto.tr.html 9 Apr 2020 15:59:12 -0000 1.1
@@ -0,0 +1,169 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/fdl-howto.en.html" -->
+
+<!--#include virtual="/server/header.tr.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>GNU FDL Kullanımı Hakkında Ä°puçları - GNU Projesi - Ãzgür
Yazılım Vakfı</title>
+
+<!--#include virtual="/licenses/po/fdl-howto.translist" -->
+<!--#include virtual="/server/banner.tr.html" -->
+<h2>GNU Ãzgür Belgeleme Lisansının Kullanımı Hakkında Ä°puçları</h2>
+
+<p>Bu yazı belgelerin <a href="/licenses/fdl.html">GNU Ãzgür Belgeleme
+Lisansı</a> kapsamında nasıl yayınlanabileceÄine iliÅkin kısa bir
+açıklamadır. GNU GPL gibi GNU yazılım lisansları için <a
+href="/licenses/gpl-howto.html">ayrı bir sayfamız</a> var.</p>
+
+<dl>
+<dt><a href="/licenses/fdl-howto-opt.html">FDL'nin isteÄe baÄlı özellikleri
+nasıl kullanılır?</a></dt>
+<dd>
+FDL'nin isteÄe baÄlı özelliklerinin nasıl kullanılacaÄını ele alan <a
+href="/licenses/fdl-howto-opt.html">ayrı bir sayfamız</a> var.</dd>
+
+<dt>Lisans bildirimi nereye koyulmalıdır?</dt>
+<dd>
+Lisans bildiriminin tamamını belgenizin dosyasındaki “ana” metne
+yerleÅtirmek yeterlidir. ÃrneÄin, <cite>Emacs Lisp BaÅvuru Kılavuzu</cite>
+ile <code>elisp.texi</code>'nin içerdiÄi birçok dosya var. Tam bildirimi
+<code>elisp.texi</code> dosyasında tutuyoruz ve diÄer dosyalara da basitçe
+Åunu yazıyoruz:
+
+<pre>
+@c - * - texinfo - * -
+@c Bu, GNU Emacs Lisp BaÅvuru Kılavuzunun bir parçasıdır.
+@c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1999
+@c Ãzgür Yazılım Vakfı, Inc.
+@c Kopyalama koÅulları için elisp.texi dosyasına bakın.
+</pre></dd>
+
+<dt>Belgemi düzgün bir Åekilde oluÅturmak için gereken betiklerle ne
yapmalıyım?</dt>
+<dd>
+Bu ilgili betikleri GNU FDL koÅullarıyla yayınlamanızı öneririz.
Elbette, bu
+betikler genellikle diÄer görevler için de yararlıysa GNU GPL
koÅullarıyla
+ayrı olarak yayınlamak da iyi bir fikirdir.</dd>
+
+<dt>Belgenin deÄiÅmez bölümlerinin olması gerekli midir?</dt>
+<dd>
+Hayır. Bir belgenin deÄiÅmez bölümlerinin olmaması tamamen kabul
edilebilir.</dd>
+
+<dt>Belgede bazı deÄiÅmez bölümler olduÄundan emin olmam gerekir mi?</dt>
+<dd>
+Ãzellikle gerekmiyor. Bir bölümün içeriÄinin deÄiÅmemesi gerekiyorsa o
kısmı
+deÄiÅmez yapın.</dd>
+
+<dt>DeÄiÅmez bölümlerden kaçınmaya çalıÅmalı mıyım?</dt>
+<dd>
+Ãzellikle gerekmiyor. Bir bölümün içeriÄinin deÄiÅmemesi gerekiyorsa o
kısmı
+deÄiÅmez yapın.</dd>
+
+<dt>Bir bölüm ne zaman deÄiÅmez olmalıdır?</dt>
+<dd>
+Her Åeyden önce, teknik belgeyle etkileÅimde olan bir bölümün deÄiÅmez
+<em>olamayacaÄını</em> aklınızda bulundurun. Yalnızca ikincil bir bölüm
+deÄiÅmez olabilir ve teknik bir bölüm ikincil bir bölüm deÄildir.
+<p>
+EÄer ilgili bölüm GNU GPL'nin bir kopyası gibi deÄiÅtirmenize izin
+verilmeyen bir metinse, <em>deÄiÅmez</em> olmalıdır. Onu deÄiÅtirme
izniniz
+yoksa, düzenleme izni veremezsiniz.</p>
+<p>
+(Bunun bir sonucu olarak sizin o metnin deÄiÅtirilmesine müsaade etme
+izniniz yoksa, teknik malzemeye iliÅkin önceden mevcut olan metni
+<em>kullanamazsınız</em>.)</p>
+<p>
+Bir bölüm özgür yazılım felsefesini tartıÅtıÄında, o bölümü
deÄiÅmez yapmak
+iyi bir fikirdir. ÃrneÄin, GNU Bildirisi'ni bir kılavuza
yerleÅtirdiÄimizde
+veya özgür belgelemenin neden önemli olduÄunu açıklayan bir bölüm
+eklediÄimizde, bu bölümü deÄiÅmez yaparız.</p></dd>
+</dl>
+
+<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 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 © 2000, 2001, 2008, 2009, 2014 Free Software Foundation,
Inc.</p>
+
+<p>Bu sayfa <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.tr">Creative
+Commons Atıf-Türetilemez 3.0 BirleÅik Devletler 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:59:12 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
Index: licenses/po/fdl-howto.tr-en.html
===================================================================
RCS file: licenses/po/fdl-howto.tr-en.html
diff -N licenses/po/fdl-howto.tr-en.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ licenses/po/fdl-howto.tr-en.html 9 Apr 2020 15:59:12 -0000 1.1
@@ -0,0 +1,145 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>Tips on Using the GNU FDL
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/fdl-howto.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Tips on Using the GNU Free Documentation License</h2>
+
+<p>This is a brief explanation of how to place a document under the <a
+href="/licenses/fdl.html">GNU Free Documentation License</a>. For the
+GNU software licenses, such as the GNU GPL, we have a <a
+href="/licenses/gpl-howto.html">separate page</a>.</p>
+
+<dl>
+<dt><a href="/licenses/fdl-howto-opt.html">How does one use the
+optional features of the FDL?</a></dt>
+<dd>
+We have a <a href="/licenses/fdl-howto-opt.html">separate page</a> that
+discusses how to use the optional features of the FDL.</dd>
+
+<dt>Where must one put the license notification?</dt>
+<dd>
+It is sufficient to put the full license notice in the
+“main” file of your document. For example, with
+the <cite>Emacs Lisp Reference Manual</cite>, we have many files
+included by <code>elisp.texi</code>. We keep the full notification
+in <code>elisp.texi</code>, and in the other files we simply write:
+
+<pre>
+@c -*-texinfo-*-
+@c This is part of the GNU Emacs Lisp Reference Manual.
+@c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1999
+@c Free Software Foundation, Inc.
+@c See the file elisp.texi for copying conditions.
+</pre></dd>
+
+<dt>What do I do with scripts that are needed to render my document
+properly?</dt>
+<dd>
+We recommend you release these scripts under the GNU FDL as well. Of
+course, if these scripts are generally useful for other tasks, it is a
+good idea to release them separately under the GNU GPL.</dd>
+
+<dt>Is it required for the document to have invariant sections?</dt>
+<dd>
+No. It is perfectly acceptable for a document to have no invariant
+sections.</dd>
+
+<dt>Should I try to make sure the document has some invariant
+sections?</dt>
+<dd>
+Not particularly. If a section's contents ought to be invariant, make
+it invariant.</dd>
+
+<dt>Should I try to avoid invariant sections?</dt>
+<dd>
+Not particularly. If a section's contents ought to be invariant, make
+it invariant.</dd>
+
+<dt>When should a section be invariant?</dt>
+<dd>
+First of all, keep in mind that a section that treats technical
+material <em>cannot</em> be invariant. Only a secondary section can
+be invariant, and a technical section is not a secondary section.
+<p>
+If the section is text that you're not allowed to modify, such as a
+copy of the GNU GPL, then it <em>must</em> be invariant. You can't
+give permission to modify it if you don't have permission to modify
+it.</p>
+<p>
+(One consequence is that you <em>cannot use</em> preexisting text
+which covers technical material if you don't have permission to allow
+modification of that text.)</p>
+<p>
+When a section discusses the philosophy of free software, it is a good
+idea to make that section invariant. For instance, when we put the
+GNU Manifesto in a manual, or when we include a section explaining why
+free documentation is important, we make that section
+invariant.</p></dd>
+</dl>
+
+</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 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 © 2000, 2001, 2008, 2009, 2014 Free Software Foundation,
Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2020/04/09 15:59:12 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- www gnu/po/why-programs-should-be-shared.transl...,
GNUN <=