trans-coord/gnun gnu/po/linux-and-gnu.bg.po gnu...

[Yavor Doganov]

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Yavor Doganov <yavor>   10/09/24 18:25:22

Modified files:
        gnun/gnu/po    : linux-and-gnu.bg.po linux-and-gnu.pot 
        gnun/philosophy/po: free-sw.af.po free-sw.bg.po free-sw.pot 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/gnu/po/linux-and-gnu.bg.po?cvsroot=trans-coord&r1=1.14&r2=1.15
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/gnu/po/linux-and-gnu.pot?cvsroot=trans-coord&r1=1.12&r2=1.13
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/philosophy/po/free-sw.af.po?cvsroot=trans-coord&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/philosophy/po/free-sw.bg.po?cvsroot=trans-coord&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/philosophy/po/free-sw.pot?cvsroot=trans-coord&r1=1.21&r2=1.22

Patches:
Index: gnu/po/linux-and-gnu.bg.po
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/gnu/po/linux-and-gnu.bg.po,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -b -r1.14 -r1.15
--- gnu/po/linux-and-gnu.bg.po  23 Sep 2009 18:25:10 -0000      1.14
+++ gnu/po/linux-and-gnu.bg.po  24 Sep 2010 18:25:21 -0000      1.15
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: linux-and-gnu.html\n"
-"POT-Creation-Date: 2009-09-23 14:25-0300\n"
+"POT-Creation-Date: 2010-09-24 14:25-0300\n"
 "PO-Revision-Date: 2008-03-30 16:26+0300\n"
 "Last-Translator: Yavor Doganov <address@hidden>\n"
 "Language-Team: Bulgarian <address@hidden>\n"
@@ -504,14 +504,23 @@
 "го комбинирате с GNU или BSD, както и да 
замените липсващите части на ядрото."
 
 # type: Content of: <ol><li>
+#, fuzzy
+#| msgid ""
+#| "<a id=\"gnubsd\"></a>On the other hand, in the years since this article "
+#| "was written, the GNU C Library has been ported to the FreeBSD kernel, "
+#| "which made it possible to combine the GNU system with that kernel.  Just "
+#| "as with GNU/Linux, these are indeed variants of GNU, and are therefore "
+#| "called GNU/kFreeBSD and GNU/kNetBSD depending on the kernel of the "
+#| "system.  Ordinary users on typical desktops can hardly distinguish "
+#| "between GNU/Linux and GNU/*BSD."
 msgid ""
 "<a id=\"gnubsd\"></a>On the other hand, in the years since this article was "
-"written, the GNU C Library has been ported to the FreeBSD kernel, which made "
-"it possible to combine the GNU system with that kernel.  Just as with GNU/"
-"Linux, these are indeed variants of GNU, and are therefore called GNU/"
-"kFreeBSD and GNU/kNetBSD depending on the kernel of the system.  Ordinary "
-"users on typical desktops can hardly distinguish between GNU/Linux and GNU/"
-"*BSD."
+"written, the GNU C Library has been ported to several versions of the BSD "
+"kernel, which made it straightforward to combine the GNU system with that "
+"kernel.  Just as with GNU/Linux, these are indeed variants of GNU, and are "
+"therefore called, for instance, GNU/kFreeBSD and GNU/kNetBSD depending on "
+"the kernel of the system.  Ordinary users on typical desktops can hardly "
+"distinguish between GNU/Linux and GNU/*BSD."
 msgstr ""
 "<a id=\"gnubsd\"></a>От друга страна, в годините 
след написването на тази "
 "статия, библиотеката на GNU за Си беше 
адаптирана към ядрото FreeBSD, което "

Index: gnu/po/linux-and-gnu.pot
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/gnu/po/linux-and-gnu.pot,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- gnu/po/linux-and-gnu.pot    23 Sep 2009 18:25:10 -0000      1.12
+++ gnu/po/linux-and-gnu.pot    24 Sep 2010 18:25:21 -0000      1.13
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2009-09-23 14:25-0300\n"
+"POT-Creation-Date: 2010-09-24 14:25-0300\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <address@hidden>\n"
 "Language-Team: LANGUAGE <address@hidden>\n"
@@ -313,12 +313,12 @@
 # type: Content of: <ol><li>
 msgid ""
 "<a id=\"gnubsd\"></a>On the other hand, in the years since this article was "
-"written, the GNU C Library has been ported to the FreeBSD kernel, which made "
-"it possible to combine the GNU system with that kernel.  Just as with "
-"GNU/Linux, these are indeed variants of GNU, and are therefore called "
-"GNU/kFreeBSD and GNU/kNetBSD depending on the kernel of the system.  "
-"Ordinary users on typical desktops can hardly distinguish between GNU/Linux "
-"and GNU/*BSD."
+"written, the GNU C Library has been ported to several versions of the BSD "
+"kernel, which made it straightforward to combine the GNU system with that "
+"kernel.  Just as with GNU/Linux, these are indeed variants of GNU, and are "
+"therefore called, for instance, GNU/kFreeBSD and GNU/kNetBSD depending on "
+"the kernel of the system.  Ordinary users on typical desktops can hardly "
+"distinguish between GNU/Linux and GNU/*BSD."
 msgstr ""
 
 #. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.

Index: philosophy/po/free-sw.af.po
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/philosophy/po/free-sw.af.po,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- philosophy/po/free-sw.af.po 1 Jul 2010 18:25:21 -0000       1.24
+++ philosophy/po/free-sw.af.po 24 Sep 2010 18:25:22 -0000      1.25
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: free-sw.html\n"
-"POT-Creation-Date: 2010-07-01 14:25-0300\n"
+"POT-Creation-Date: 2010-09-24 14:25-0300\n"
 "PO-Revision-Date: 2008-02-19 07:45+0200\n"
 "Last-Translator: Renier Maritz <address@hidden>\n"
 "Language-Team: \n"
@@ -332,32 +332,29 @@
 msgstr ""
 
 # type: Content of: <p>
-#, fuzzy
 msgid ""
 "However, rules about how to package a modified version are acceptable, if "
 "they don't substantively limit your freedom to release modified versions, or "
-"your freedom to make and use modified versions privately.  Rules that &ldquo;"
-"if you make your version available in this way, you must make it available "
-"in that way also&rdquo; can be acceptable too, on the same condition.  (Note "
-"that such a rule still leaves you the choice of whether to publish your "
-"version at all.)  Rules that require release of source code to the users for "
-"versions that you put into public use are also acceptable.  It is also "
-"acceptable for the license to require that you identify your modifications "
-"as yours, or that, if you have distributed a modified version and a previous "
-"developer asks for a copy of it, you must send one."
-msgstr ""
-"Reëls oor hoe om 'n veranderde pakket te verpak is aanvaarbaar as hulle nie "
-"jou vryheid beduidend beperk om veranderde weergawes te versprei nie of jou "
-"vryheid om veranderings privaat te maak en te gebruik nie.  Re&euml;ls wat "
-"van jou vereis om 'n pakket op 'n besondere manier beskikbaar te maak indien "
-"jy dit op 'n andermanier doen is ook aanvaarbaar op dieselfde voorwaardes "
-"(Neem kennis dat so 'n re&euml;l jou nog steeds vrystaan om te besluit of jy "
-"jou weergawe wil publiseer aldan nie).  Re&euml;ls wat die vrystel van die "
-"bronkode vereis aan gebruikers van weergawes wat jy vir openbare gebruik "
-"beskikbaar stel is ook aanvaarbaar.  Dit isook aanvaarbaar dat die lisensie "
-"vereis dat, as jy 'n veranderdeweergawe versprei het, jy dit op aanvraag aan "
-"die vorige ontwikkelaarmoet stuur of dat jy jouself op veranderinge "
-"identifiseer."
+"your freedom to make and use modified versions privately.  Thus, it is "
+"acceptable for the license to require that you change the name of the "
+"modified version, remove a logo, or identify your modifications as yours.  "
+"As long as these requirements are not so burdensome that they effectively "
+"hamper you from releasing your changes, they are acceptable; you're already "
+"making other changes to the program, so you won't have trouble making a few "
+"more."
+msgstr ""
+
+# type: Content of: <p>
+msgid ""
+"Rules that &ldquo;if you make your version available in this way, you must "
+"make it available in that way also&rdquo; can be acceptable too, on the same "
+"condition.  An example of such an acceptable rule is one saying that if you "
+"have distributed a modified version and a previous developer asks for a copy "
+"of it, you must send one.  (Note that such a rule still leaves you the "
+"choice of whether to distribute your version at all.)  Rules that require "
+"release of source code to the users for versions that you put into public "
+"use are also acceptable."
+msgstr ""
 
 # type: Content of: <p>
 #, fuzzy
@@ -848,6 +845,35 @@
 
 # type: Content of: <p>
 #, fuzzy
+#~ msgid ""
+#~ "However, rules about how to package a modified version are acceptable, if "
+#~ "they don't substantively limit your freedom to release modified versions, "
+#~ "or your freedom to make and use modified versions privately.  Rules that "
+#~ "&ldquo;if you make your version available in this way, you must make it "
+#~ "available in that way also&rdquo; can be acceptable too, on the same "
+#~ "condition.  (Note that such a rule still leaves you the choice of whether "
+#~ "to publish your version at all.)  Rules that require release of source "
+#~ "code to the users for versions that you put into public use are also "
+#~ "acceptable.  It is also acceptable for the license to require that you "
+#~ "identify your modifications as yours, or that, if you have distributed a "
+#~ "modified version and a previous developer asks for a copy of it, you must "
+#~ "send one."
+#~ msgstr ""
+#~ "Reëls oor hoe om 'n veranderde pakket te verpak is aanvaarbaar as hulle "
+#~ "nie jou vryheid beduidend beperk om veranderde weergawes te versprei nie "
+#~ "of jou vryheid om veranderings privaat te maak en te gebruik nie.  "
+#~ "Re&euml;ls wat van jou vereis om 'n pakket op 'n besondere manier "
+#~ "beskikbaar te maak indien jy dit op 'n andermanier doen is ook "
+#~ "aanvaarbaar op dieselfde voorwaardes (Neem kennis dat so 'n re&euml;l jou "
+#~ "nog steeds vrystaan om te besluit of jy jou weergawe wil publiseer aldan "
+#~ "nie).  Re&euml;ls wat die vrystel van die bronkode vereis aan gebruikers "
+#~ "van weergawes wat jy vir openbare gebruik beskikbaar stel is ook "
+#~ "aanvaarbaar.  Dit isook aanvaarbaar dat die lisensie vereis dat, as jy 'n "
+#~ "veranderdeweergawe versprei het, jy dit op aanvraag aan die vorige "
+#~ "ontwikkelaarmoet stuur of dat jy jouself op veranderinge identifiseer."
+
+# type: Content of: <p>
+#, fuzzy
 #~| msgid ""
 #~| "See <a href=\"/philosophy/categories.html\">Categories of Free Software</"
 #~| "a> for a description of how <q>free software,</q> <q>copylefted "

Index: philosophy/po/free-sw.bg.po
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/philosophy/po/free-sw.bg.po,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- philosophy/po/free-sw.bg.po 9 Aug 2010 16:08:59 -0000       1.27
+++ philosophy/po/free-sw.bg.po 24 Sep 2010 18:25:22 -0000      1.28
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: free-sw.html\n"
-"POT-Creation-Date: 2010-07-01 14:25-0300\n"
+"POT-Creation-Date: 2010-09-24 14:25-0300\n"
 "PO-Revision-Date: 2010-08-09 19:08+0300\n"
 "Last-Translator: Yavor Doganov <address@hidden>\n"
 "Language-Team: Bulgarian <address@hidden>\n"
@@ -339,31 +339,29 @@
 msgstr ""
 
 # type: Content of: <p>
-#, fuzzy
 msgid ""
 "However, rules about how to package a modified version are acceptable, if "
 "they don't substantively limit your freedom to release modified versions, or "
-"your freedom to make and use modified versions privately.  Rules that &ldquo;"
-"if you make your version available in this way, you must make it available "
-"in that way also&rdquo; can be acceptable too, on the same condition.  (Note "
-"that such a rule still leaves you the choice of whether to publish your "
-"version at all.)  Rules that require release of source code to the users for "
-"versions that you put into public use are also acceptable.  It is also "
-"acceptable for the license to require that you identify your modifications "
-"as yours, or that, if you have distributed a modified version and a previous "
-"developer asks for a copy of it, you must send one."
-msgstr ""
-"Правила за начина на пакетиране на 
променена версия са приемливи, стига по "
-"същество да не пречат на свободата ви да я 
разпространявате или да "
-"използвате версии, които сте променили 
самостоятелно.  Правила, че „ако "
-"направите версията си достъпна по този 
начин, трябва да я направите достъпна "
-"и по този начин“, може да са приемливи при 
същото условие.  (Имайте предвид, "
-"че такова правило трябва да ви оставя 
избора дали въобще да разпространявате "
-"своята си версия.)  Правила, които изискват 
да публикувате изходния код на "
-"версии, които сте направили достъпни за 
публично ползване, също са "
-"допустими.  Допустимо е лицензът да 
изисква, ако разпространявате променена "
-"версия и някой от предишните разработчици 
ви поиска нейно копие, да трябва "
-"да му го пратите, както и изискването да 
обозначите промените си."
+"your freedom to make and use modified versions privately.  Thus, it is "
+"acceptable for the license to require that you change the name of the "
+"modified version, remove a logo, or identify your modifications as yours.  "
+"As long as these requirements are not so burdensome that they effectively "
+"hamper you from releasing your changes, they are acceptable; you're already "
+"making other changes to the program, so you won't have trouble making a few "
+"more."
+msgstr ""
+
+# type: Content of: <p>
+msgid ""
+"Rules that &ldquo;if you make your version available in this way, you must "
+"make it available in that way also&rdquo; can be acceptable too, on the same "
+"condition.  An example of such an acceptable rule is one saying that if you "
+"have distributed a modified version and a previous developer asks for a copy "
+"of it, you must send one.  (Note that such a rule still leaves you the "
+"choice of whether to distribute your version at all.)  Rules that require "
+"release of source code to the users for versions that you put into public "
+"use are also acceptable."
+msgstr ""
 
 # type: Content of: <p>
 #, fuzzy
@@ -879,6 +877,35 @@
 
 # type: Content of: <p>
 #, fuzzy
+#~ msgid ""
+#~ "However, rules about how to package a modified version are acceptable, if "
+#~ "they don't substantively limit your freedom to release modified versions, "
+#~ "or your freedom to make and use modified versions privately.  Rules that "
+#~ "&ldquo;if you make your version available in this way, you must make it "
+#~ "available in that way also&rdquo; can be acceptable too, on the same "
+#~ "condition.  (Note that such a rule still leaves you the choice of whether "
+#~ "to publish your version at all.)  Rules that require release of source "
+#~ "code to the users for versions that you put into public use are also "
+#~ "acceptable.  It is also acceptable for the license to require that you "
+#~ "identify your modifications as yours, or that, if you have distributed a "
+#~ "modified version and a previous developer asks for a copy of it, you must "
+#~ "send one."
+#~ msgstr ""
+#~ "Правила за начина на пакетиране на 
променена версия са приемливи, стига "
+#~ "по същество да не пречат на свободата ви 
да я разпространявате или да "
+#~ "използвате версии, които сте променили 
самостоятелно.  Правила, че „ако "
+#~ "направите версията си достъпна по този 
начин, трябва да я направите "
+#~ "достъпна и по този начин“, може да са 
приемливи при същото условие.  "
+#~ "(Имайте предвид, че такова правило 
трябва да ви оставя избора дали въобще "
+#~ "да разпространявате своята си версия.)  
Правила, които изискват да "
+#~ "публикувате изходния код на версии, 
които сте направили достъпни за "
+#~ "публично ползване, също са допустими.  
Допустимо е лицензът да изисква, "
+#~ "ако разпространявате променена версия и 
някой от предишните разработчици "
+#~ "ви поиска нейно копие, да трябва да му го 
пратите, както и изискването да "
+#~ "обозначите промените си."
+
+# type: Content of: <p>
+#, fuzzy
 #~| msgid ""
 #~| "See <a href=\"/philosophy/categories.html\">Categories of Free Software</"
 #~| "a> for a description of how <q>free software,</q> <q>copylefted "

Index: philosophy/po/free-sw.pot
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/philosophy/po/free-sw.pot,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- philosophy/po/free-sw.pot   1 Jul 2010 18:25:21 -0000       1.21
+++ philosophy/po/free-sw.pot   24 Sep 2010 18:25:22 -0000      1.22
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2010-07-01 14:25-0300\n"
+"POT-Creation-Date: 2010-09-24 14:25-0300\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <address@hidden>\n"
 "Language-Team: LANGUAGE <address@hidden>\n"
@@ -214,15 +214,25 @@
 msgid ""
 "However, rules about how to package a modified version are acceptable, if "
 "they don't substantively limit your freedom to release modified versions, or "
-"your freedom to make and use modified versions privately.  Rules that "
-"&ldquo;if you make your version available in this way, you must make it "
-"available in that way also&rdquo; can be acceptable too, on the same "
-"condition.  (Note that such a rule still leaves you the choice of whether to "
-"publish your version at all.)  Rules that require release of source code to "
-"the users for versions that you put into public use are also acceptable.  It "
-"is also acceptable for the license to require that you identify your "
-"modifications as yours, or that, if you have distributed a modified version "
-"and a previous developer asks for a copy of it, you must send one."
+"your freedom to make and use modified versions privately.  Thus, it is "
+"acceptable for the license to require that you change the name of the "
+"modified version, remove a logo, or identify your modifications as yours.  "
+"As long as these requirements are not so burdensome that they effectively "
+"hamper you from releasing your changes, they are acceptable; you're already "
+"making other changes to the program, so you won't have trouble making a few "
+"more."
+msgstr ""
+
+# type: Content of: <p>
+msgid ""
+"Rules that &ldquo;if you make your version available in this way, you must "
+"make it available in that way also&rdquo; can be acceptable too, on the same "
+"condition.  An example of such an acceptable rule is one saying that if you "
+"have distributed a modified version and a previous developer asks for a copy "
+"of it, you must send one.  (Note that such a rule still leaves you the "
+"choice of whether to distribute your version at all.)  Rules that require "
+"release of source code to the users for versions that you put into public "
+"use are also acceptable."
 msgstr ""
 
 # type: Content of: <p>