[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/gnu/po gnu-linux-faq.ar.po gnu-linux-faq.ca...
|
From: |
GNUN |
|
Subject: |
www/gnu/po gnu-linux-faq.ar.po gnu-linux-faq.ca... |
|
Date: |
Thu, 18 Aug 2016 20:28:27 +0000 (UTC) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 16/08/18 20:28:27
Modified files:
gnu/po : gnu-linux-faq.ar.po gnu-linux-faq.ca.po
gnu-linux-faq.de.po gnu-linux-faq.es.po
gnu-linux-faq.fr.po gnu-linux-faq.hr-diff.html
gnu-linux-faq.hr.po gnu-linux-faq.it.po
gnu-linux-faq.ja.po gnu-linux-faq.ko.po
gnu-linux-faq.nl-diff.html gnu-linux-faq.nl.po
gnu-linux-faq.pl.po gnu-linux-faq.pot
gnu-linux-faq.ru.po gnu-linux-faq.sq.po
gnu-linux-faq.sr.po gnu-linux-faq.tr.po
gnu-linux-faq.uk.po
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.ar.po?cvsroot=www&r1=1.51&r2=1.52
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.ca.po?cvsroot=www&r1=1.76&r2=1.77
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.de.po?cvsroot=www&r1=1.91&r2=1.92
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.es.po?cvsroot=www&r1=1.98&r2=1.99
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.fr.po?cvsroot=www&r1=1.92&r2=1.93
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.hr-diff.html?cvsroot=www&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.hr.po?cvsroot=www&r1=1.26&r2=1.27
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.it.po?cvsroot=www&r1=1.24&r2=1.25
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.ja.po?cvsroot=www&r1=1.65&r2=1.66
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.ko.po?cvsroot=www&r1=1.13&r2=1.14
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.nl-diff.html?cvsroot=www&r1=1.34&r2=1.35
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.nl.po?cvsroot=www&r1=1.39&r2=1.40
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.pl.po?cvsroot=www&r1=1.69&r2=1.70
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.pot?cvsroot=www&r1=1.43&r2=1.44
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.ru.po?cvsroot=www&r1=1.82&r2=1.83
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.sq.po?cvsroot=www&r1=1.84&r2=1.85
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.sr.po?cvsroot=www&r1=1.46&r2=1.47
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.tr.po?cvsroot=www&r1=1.50&r2=1.51
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-linux-faq.uk.po?cvsroot=www&r1=1.23&r2=1.24
Patches:
Index: gnu-linux-faq.ar.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.ar.po,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -b -r1.51 -r1.52
--- gnu-linux-faq.ar.po 18 Aug 2016 17:00:15 -0000 1.51
+++ gnu-linux-faq.ar.po 18 Aug 2016 20:28:26 -0000 1.52
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2016-08-18 16:55+0000\n"
+"POT-Creation-Date: 2016-08-18 20:25+0000\n"
"PO-Revision-Date: 2010-03-30 16:12+0300\n"
"Last-Translator: Hossam Hossny <address@hidden>\n"
"Language-Team: Arabic <>\n"
@@ -225,6 +225,19 @@
# type: Content of: <ul><li>
#. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write “GNU/"
+#| "Linux” instead of “GNU Linux”?</a>"
+msgid ""
+"<a href=\"#long1\" id=\"TOClong1\">How about calling the system “"
+"GliNUx” (instead of “GNU/Linux”)?</a>"
+msgstr ""
+"<a href=\"#whyslash\" id=\"TOCwhyslash\">ÙÙ
اذا تÙتبÙÙ
”غÙÙ/"
+"ÙÙÙÙس“ بدÙا Ù
Ù ”غÙÙ ÙÙÙÙسx“Ø</a>"
+
+# type: Content of: <ul><li>
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#long2\" id=\"TOClong2\">The problem with “GNU/Linux” "
"is that it is too long. Why should I go to the trouble of saying “GNU/"
@@ -1494,6 +1507,35 @@
# type: Content of: <dl><dt>
#. type: Content of: <dl><dt>
+#, fuzzy
+#| msgid ""
+#| "Why do you write “GNU/Linux” instead of “GNU "
+#| "Linux”? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+#| "\">#whyslash</a>)</span>"
+msgid ""
+"How about calling the system “GliNUx” (instead of “GNU/"
+"Linux”)? <span class=\"anchor-reference-id\">(<a href="
+"\"#long1\">#long1</a>)</span>"
+msgstr ""
+"ÙÙ
اذا تÙتبÙÙ ”غÙÙ/ÙÙÙÙس“ بدÙا Ù
Ù
”غÙÙ ÙÙÙÙسx“Ø <span "
+"class=\"anchor-reference-id\">(<a href=\"#whyslash\">#whyslash</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The name “GNU” does not visibly appear in “Glinux,” "
+"so most people would not notice it is there. Even if it is capitalized as "
+"“GliNUx,” most people would not realize that it contains a "
+"reference to GNU."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It would be comparable to writing “GNU/Linux,” but putting "
+"“GNU/” in print so small that most people could not read it."
+msgstr ""
+
+# type: Content of: <dl><dt>
+#. type: Content of: <dl><dt>
msgid ""
"The problem with “GNU/Linux” is that it is too long. Why should "
"I go to the trouble of saying “GNU/”? <span class=\"anchor-"
Index: gnu-linux-faq.ca.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.ca.po,v
retrieving revision 1.76
retrieving revision 1.77
diff -u -b -r1.76 -r1.77
--- gnu-linux-faq.ca.po 18 Aug 2016 17:00:15 -0000 1.76
+++ gnu-linux-faq.ca.po 18 Aug 2016 20:28:26 -0000 1.77
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: gnu-linux-faq\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2016-08-18 16:55+0000\n"
+"POT-Creation-Date: 2016-08-18 20:25+0000\n"
"PO-Revision-Date: 2016-04-23 18:06+0200\n"
"Last-Translator: Miquel Puigpelat <address@hidden>\n"
"Language-Team: Catalan <address@hidden>\n"
@@ -234,6 +234,19 @@
# type: Content of: <ul><li>
#. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write “GNU/"
+#| "Linux” instead of “GNU Linux”?</a>"
+msgid ""
+"<a href=\"#long1\" id=\"TOClong1\">How about calling the system “"
+"GliNUx” (instead of “GNU/Linux”)?</a>"
+msgstr ""
+"<a href=\"#whyslash\" id=\"TOCwhyslash\">Per què escriviu âGNU/Linuxâ en
"
+"lloc de âGNU Linuxâ?</a>"
+
+# type: Content of: <ul><li>
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#long2\" id=\"TOClong2\">The problem with “GNU/Linux” "
"is that it is too long. Why should I go to the trouble of saying “GNU/"
@@ -1575,6 +1588,35 @@
# type: Content of: <dl><dt>
#. type: Content of: <dl><dt>
+#, fuzzy
+#| msgid ""
+#| "Why do you write “GNU/Linux” instead of “GNU "
+#| "Linux”? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+#| "\">#whyslash</a>)</span>"
+msgid ""
+"How about calling the system “GliNUx” (instead of “GNU/"
+"Linux”)? <span class=\"anchor-reference-id\">(<a href="
+"\"#long1\">#long1</a>)</span>"
+msgstr ""
+"Per què escriviu âGNU/Linuxâ en lloc de âGNU Linuxâ? <span
class=\"anchor-"
+"reference-id\">(<a href=\"#whyslash\">#whyslash</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The name “GNU” does not visibly appear in “Glinux,” "
+"so most people would not notice it is there. Even if it is capitalized as "
+"“GliNUx,” most people would not realize that it contains a "
+"reference to GNU."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It would be comparable to writing “GNU/Linux,” but putting "
+"“GNU/” in print so small that most people could not read it."
+msgstr ""
+
+# type: Content of: <dl><dt>
+#. type: Content of: <dl><dt>
msgid ""
"The problem with “GNU/Linux” is that it is too long. Why should "
"I go to the trouble of saying “GNU/”? <span class=\"anchor-"
Index: gnu-linux-faq.de.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.de.po,v
retrieving revision 1.91
retrieving revision 1.92
diff -u -b -r1.91 -r1.92
--- gnu-linux-faq.de.po 18 Aug 2016 17:00:15 -0000 1.91
+++ gnu-linux-faq.de.po 18 Aug 2016 20:28:26 -0000 1.92
@@ -8,7 +8,7 @@
msgstr ""
"Project-Id-Version: gnu-linux-faq.html\n"
"Report-Msgid-Bugs-To: Webmasters <address@hidden>\n"
-"POT-Creation-Date: 2016-08-18 16:55+0000\n"
+"POT-Creation-Date: 2016-08-18 20:25+0000\n"
"PO-Revision-Date: 2015-12-14 22:00+0200\n"
"Last-Translator: Jоегg Kоhпе <joeko (AT) online [PUNKT] de>\n"
"Language-Team: German <address@hidden>\n"
@@ -217,6 +217,22 @@
"empfehlen?</a>"
#. type: Content of: <ul><li>
+# | <a [-href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write
+# | “GNU/Linux” instead-] {+href=\"#long1\" id=\"TOClong1\">How
+# | about calling the system “GliNUx” (instead+} of [-“GNU
+# | Linux”?</a>-] {+“GNU/Linux”)?</a>+}
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write “GNU/"
+#| "Linux” instead of “GNU Linux”?</a>"
+msgid ""
+"<a href=\"#long1\" id=\"TOClong1\">How about calling the system “"
+"GliNUx” (instead of “GNU/Linux”)?</a>"
+msgstr ""
+"<a href=\"#whyslash\" id=\"TOCwhyslash\">Warum <em><strong>GNU/Linux</"
+"strong></em> statt <em>âGNU Linuxâ</em> schreiben?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#long2\" id=\"TOClong2\">The problem with “GNU/Linux” "
"is that it is too long. Why should I go to the trouble of saying “GNU/"
@@ -1492,6 +1508,40 @@
"Linux</strong>."
#. type: Content of: <dl><dt>
+# | [-Why do you write “GNU/Linux” instead-]{+How about calling
+# | the system “GliNUx” (instead+} of [-“GNU Linux”?-]
+# | {+“GNU/Linux”)?+} <span class=\"anchor-reference-id\">(<a
+# | [-href=\"#whyslash\">#whyslash</a>)</span>-]
+# | {+href=\"#long1\">#long1</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Why do you write “GNU/Linux” instead of “GNU "
+#| "Linux”? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+#| "\">#whyslash</a>)</span>"
+msgid ""
+"How about calling the system “GliNUx” (instead of “GNU/"
+"Linux”)? <span class=\"anchor-reference-id\">(<a href="
+"\"#long1\">#long1</a>)</span>"
+msgstr ""
+"Warum <em><strong>GNU/Linux</strong></em> statt <em>âGNU Linuxâ</em> "
+"schreiben? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+"\">#whyslash</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The name “GNU” does not visibly appear in “Glinux,” "
+"so most people would not notice it is there. Even if it is capitalized as "
+"“GliNUx,” most people would not realize that it contains a "
+"reference to GNU."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It would be comparable to writing “GNU/Linux,” but putting "
+"“GNU/” in print so small that most people could not read it."
+msgstr ""
+
+#. type: Content of: <dl><dt>
msgid ""
"The problem with “GNU/Linux” is that it is too long. Why should "
"I go to the trouble of saying “GNU/”? <span class=\"anchor-"
Index: gnu-linux-faq.es.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.es.po,v
retrieving revision 1.98
retrieving revision 1.99
diff -u -b -r1.98 -r1.99
--- gnu-linux-faq.es.po 18 Aug 2016 17:00:15 -0000 1.98
+++ gnu-linux-faq.es.po 18 Aug 2016 20:28:26 -0000 1.99
@@ -10,7 +10,7 @@
msgstr ""
"Project-Id-Version: gnu-linux-faq.es\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2016-08-18 16:55+0000\n"
+"POT-Creation-Date: 2016-08-18 20:25+0000\n"
"PO-Revision-Date: 2016-03-03 11:36+0100\n"
"Last-Translator: Javier Fdez. Retenaga <address@hidden>\n"
"Language-Team: Spanish <address@hidden>\n"
@@ -242,6 +242,23 @@
# type: Content of: <ul><li>
#. type: Content of: <ul><li>
+# | <a [-href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write
+# | “GNU/Linux” instead-] {+href=\"#long1\" id=\"TOClong1\">How
+# | about calling the system “GliNUx” (instead+} of [-“GNU
+# | Linux”?</a>-] {+“GNU/Linux”)?</a>+}
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write “GNU/"
+#| "Linux” instead of “GNU Linux”?</a>"
+msgid ""
+"<a href=\"#long1\" id=\"TOClong1\">How about calling the system “"
+"GliNUx” (instead of “GNU/Linux”)?</a>"
+msgstr ""
+"<a href=\"#whyslash\" id=\"TOCwhyslash\">¿Por qué escriben «GNU/Linux» en
"
+"lugar de «GNU Linux»?</a>"
+
+# type: Content of: <ul><li>
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#long2\" id=\"TOClong2\">The problem with “GNU/Linux” "
"is that it is too long. Why should I go to the trouble of saying “GNU/"
@@ -1594,6 +1611,40 @@
# type: Content of: <dl><dt>
#. type: Content of: <dl><dt>
+# | [-Why do you write “GNU/Linux” instead-]{+How about calling
+# | the system “GliNUx” (instead+} of [-“GNU Linux”?-]
+# | {+“GNU/Linux”)?+} <span class=\"anchor-reference-id\">(<a
+# | [-href=\"#whyslash\">#whyslash</a>)</span>-]
+# | {+href=\"#long1\">#long1</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Why do you write “GNU/Linux” instead of “GNU "
+#| "Linux”? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+#| "\">#whyslash</a>)</span>"
+msgid ""
+"How about calling the system “GliNUx” (instead of “GNU/"
+"Linux”)? <span class=\"anchor-reference-id\">(<a href="
+"\"#long1\">#long1</a>)</span>"
+msgstr ""
+"¿Por qué escriben «GNU/Linux» en lugar de «GNU Linux»? <span
class=\"anchor-"
+"reference-id\">(<a href=\"#whyslash\">#whyslash</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The name “GNU” does not visibly appear in “Glinux,” "
+"so most people would not notice it is there. Even if it is capitalized as "
+"“GliNUx,” most people would not realize that it contains a "
+"reference to GNU."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It would be comparable to writing “GNU/Linux,” but putting "
+"“GNU/” in print so small that most people could not read it."
+msgstr ""
+
+# type: Content of: <dl><dt>
+#. type: Content of: <dl><dt>
msgid ""
"The problem with “GNU/Linux” is that it is too long. Why should "
"I go to the trouble of saying “GNU/”? <span class=\"anchor-"
Index: gnu-linux-faq.fr.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.fr.po,v
retrieving revision 1.92
retrieving revision 1.93
diff -u -b -r1.92 -r1.93
--- gnu-linux-faq.fr.po 18 Aug 2016 17:00:15 -0000 1.92
+++ gnu-linux-faq.fr.po 18 Aug 2016 20:28:26 -0000 1.93
@@ -10,7 +10,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2016-08-18 16:55+0000\n"
+"POT-Creation-Date: 2016-08-18 20:25+0000\n"
"PO-Revision-Date: 2015-12-14 12:17+0100\n"
"Last-Translator: Sogal <sogal AT member.fsf.org>\n"
"Language-Team: French <address@hidden>\n"
@@ -217,6 +217,22 @@
"c'est trop long. Pourquoi ne pas recommander un nom plus court ?</a>"
#. type: Content of: <ul><li>
+# | <a [-href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write
+# | “GNU/Linux” instead-] {+href=\"#long1\" id=\"TOClong1\">How
+# | about calling the system “GliNUx” (instead+} of [-“GNU
+# | Linux”?</a>-] {+“GNU/Linux”)?</a>+}
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write “GNU/"
+#| "Linux” instead of “GNU Linux”?</a>"
+msgid ""
+"<a href=\"#long1\" id=\"TOClong1\">How about calling the system “"
+"GliNUx” (instead of “GNU/Linux”)?</a>"
+msgstr ""
+"<a href=\"#whyslash\" id=\"TOCwhyslash\">Pourquoi écrivez-vous «Â
GNU/Linux » "
+"au lieu de « GNU Linux » ?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#long2\" id=\"TOClong2\">The problem with “GNU/Linux” "
"is that it is too long. Why should I go to the trouble of saying “GNU/"
@@ -1493,6 +1509,39 @@
"loin</a>."
#. type: Content of: <dl><dt>
+# | [-Why do you write “GNU/Linux” instead-]{+How about calling
+# | the system “GliNUx” (instead+} of [-“GNU Linux”?-]
+# | {+“GNU/Linux”)?+} <span class=\"anchor-reference-id\">(<a
+# | [-href=\"#whyslash\">#whyslash</a>)</span>-]
+# | {+href=\"#long1\">#long1</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Why do you write “GNU/Linux” instead of “GNU "
+#| "Linux”? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+#| "\">#whyslash</a>)</span>"
+msgid ""
+"How about calling the system “GliNUx” (instead of “GNU/"
+"Linux”)? <span class=\"anchor-reference-id\">(<a href="
+"\"#long1\">#long1</a>)</span>"
+msgstr ""
+"Pourquoi écrivez-vous « GNU/Linux » au lieu de « GNU Linux » ?
<span class="
+"\"anchor-reference-id\">(<a href=\"#whyslash\">#whyslash</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The name “GNU” does not visibly appear in “Glinux,” "
+"so most people would not notice it is there. Even if it is capitalized as "
+"“GliNUx,” most people would not realize that it contains a "
+"reference to GNU."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It would be comparable to writing “GNU/Linux,” but putting "
+"“GNU/” in print so small that most people could not read it."
+msgstr ""
+
+#. type: Content of: <dl><dt>
msgid ""
"The problem with “GNU/Linux” is that it is too long. Why should "
"I go to the trouble of saying “GNU/”? <span class=\"anchor-"
Index: gnu-linux-faq.hr-diff.html
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.hr-diff.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnu-linux-faq.hr-diff.html 18 Aug 2016 17:00:15 -0000 1.18
+++ gnu-linux-faq.hr-diff.html 18 Aug 2016 20:28:26 -0000 1.19
@@ -11,7 +11,7 @@
</style></head>
<body><pre>
<!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: <span
class="removed"><del><strong>1.75</strong></del></span> <span
class="inserted"><ins><em>1.77</em></ins></span> -->
+<!-- Parent-Version: <span
class="removed"><del><strong>1.75</strong></del></span> <span
class="inserted"><ins><em>1.79</em></ins></span> -->
<title>GNU/Linux FAQ
- GNU Project - Free Software Foundation</title>
<!--#include virtual="/gnu/po/gnu-linux-faq.translist" -->
@@ -96,7 +96,10 @@
“GNU/Linux” is that it is too long. How about
recommending a shorter name?</a></li>
-<li><a href="#long2" id="TOClong2">The problem with
+<li><a <span class="inserted"><ins><em>href="#long1"
id="TOClong1">How about calling the system
+ “GliNUx” (instead of
“GNU/Linux”)?</a></li>
+
+<li><a</em></ins></span> href="#long2" id="TOClong2">The problem
with
“GNU/Linux” is that it is too long. Why should
I go to the trouble of saying “GNU/”?</a></li>
@@ -580,20 +583,19 @@
<span class="removed"><del><strong>That practice seems to be very
rare—we can't find any examples other
than the misuse</strong></del></span>
<span class="inserted"><ins><em>Many <a href="/distros/distros.html">
packaged and installable
-versions</em></ins></span> of <span class="removed"><del><strong>the name
“Linux”. Normally an operating system</strong></del></span> <span
class="inserted"><ins><em>GNU</a> are available. None of
them</em></ins></span> is
-<span class="removed"><del><strong>developed as a single unified project, and
the developers choose a
-name for</strong></del></span> <span class="inserted"><ins><em>called simply
+versions of GNU</a> are available. None</em></ins></span> of <span
class="inserted"><ins><em>them is called simply
“GNU”, but GNU is what they basically are.
<p>
-We expected to release</em></ins></span> the <span
class="inserted"><ins><em>GNU</em></ins></span> system <span
class="removed"><del><strong>as</strong></del></span> <span
class="inserted"><ins><em>packaged for installation, but
+We expected to release</em></ins></span> the <span
class="removed"><del><strong>name “Linux”. Normally an
operating</strong></del></span> <span
class="inserted"><ins><em>GNU</em></ins></span> system <span
class="removed"><del><strong>is
+developed as</strong></del></span> <span class="inserted"><ins><em>packaged
for installation, but
this plan was overtaken by events: in 1992 others were already
packaging GNU variants containing Linux. Starting in 1993 we
-sponsored an effort to make</em></ins></span> a <span
class="removed"><del><strong>whole.</strong></del></span> <span
class="inserted"><ins><em>better and freer GNU/Linux distribution,
+sponsored an effort to make</em></ins></span> a <span
class="removed"><del><strong>single unified project,</strong></del></span>
<span class="inserted"><ins><em>better</em></ins></span> and <span
class="inserted"><ins><em>freer GNU/Linux distribution,
called <a href="/distros/common-distros.html#Debian">Debian
-GNU/Linux</a>.</em></ins></span> The <span
class="removed"><del><strong>kernel usually does</strong></del></span> <span
class="inserted"><ins><em>founder of Debian had already chosen that name.
-We did</em></ins></span> not <span class="removed"><del><strong>have
a</strong></del></span> <span class="inserted"><ins><em>ask him to call it just
“GNU” because that was
-to be the name of a system version with the GNU Hurd kernel—which
+GNU/Linux</a>. The founder of Debian had already chosen that name.
+We did not ask him to call it just “GNU” because that was
+to be</em></ins></span> the <span class="removed"><del><strong>developers
choose a</strong></del></span> name <span class="removed"><del><strong>for the
system as</strong></del></span> <span
class="inserted"><ins><em>of</em></ins></span> a <span
class="removed"><del><strong>whole.</strong></del></span> <span
class="inserted"><ins><em>system version with the GNU Hurd kernel—which
wasn't ready yet.</p>
<p>
@@ -622,7 +624,7 @@
That practice seems to be very rare—we can't find any examples other
than the misuse of the name “Linux”. Normally an operating system
is
developed as a single unified project, and the developers choose a
-name for the system as a whole. The kernel usually does not have
a</em></ins></span>
+name for the system as a whole.</em></ins></span> The kernel usually does not
have a
name of its own—instead, people say “the kernel of
such-and-such” or
“the such-and-such kernel”.
<p>
@@ -657,7 +659,22 @@
given below</a>.</p>
</dd>
-<dt id="long2">The problem with “GNU/Linux” is that it is
too long.
+<dt <span class="inserted"><ins><em>id="long1">How about calling the
system
+ “GliNUx” (instead of “GNU/Linux”)?
+ <span class="anchor-reference-id">(<a
href="#long1">#long1</a>)</span></dt>
+
+<dd>
+<p>The name “GNU” does not visibly appear in
+“Glinux,” so most people would not notice it is there.
+Even if it is capitalized as “GliNUx,” most people would
+not realize that it contains a reference to GNU.</p>
+
+<p>It would be comparable to writing “GNU/Linux,” but
+putting “GNU/” in print so small that most people could
+not read it.</p>
+</dd>
+
+<dt</em></ins></span> id="long2">The problem with
“GNU/Linux” is that it is too long.
Why should I go to the trouble of saying “GNU/”?
<span class="anchor-reference-id">(<a
href="#long2">#long2</a>)</span></dt>
@@ -1554,7 +1571,7 @@
<span class="inserted"><ins><em><p
class="unprintable">Updated:</em></ins></span>
<!-- timestamp start -->
-$Date: 2016/08/18 17:00:15 $
+$Date: 2016/08/18 20:28:26 $
<!-- timestamp end -->
</p>
</div>
Index: gnu-linux-faq.hr.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.hr.po,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- gnu-linux-faq.hr.po 18 Aug 2016 17:00:15 -0000 1.26
+++ gnu-linux-faq.hr.po 18 Aug 2016 20:28:26 -0000 1.27
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2016-08-18 16:55+0000\n"
+"POT-Creation-Date: 2016-08-18 20:25+0000\n"
"PO-Revision-Date: 2013-05-30 22:45+0100\n"
"Last-Translator: Martina Bebek <address@hidden>\n"
"Language-Team: GNU Croatian Translation Team <address@hidden>\n"
@@ -226,6 +226,22 @@
"jest da je predugaÄak. A da predložite kraÄi naziv?</a>"
#. type: Content of: <ul><li>
+# | <a [-href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write
+# | “GNU/Linux” instead-] {+href=\"#long1\" id=\"TOClong1\">How
+# | about calling the system “GliNUx” (instead+} of [-“GNU
+# | Linux”?</a>-] {+“GNU/Linux”)?</a>+}
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write “GNU/"
+#| "Linux” instead of “GNU Linux”?</a>"
+msgid ""
+"<a href=\"#long1\" id=\"TOClong1\">How about calling the system “"
+"GliNUx” (instead of “GNU/Linux”)?</a>"
+msgstr ""
+"<a href=\"#whyslash\" id=\"TOCwhyslash\">ZaÅ¡to piÅ¡ete “GNU/"
+"Linux” umjesto “GNU Linux”?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#long2\" id=\"TOClong2\">The problem with “GNU/Linux” "
"is that it is too long. Why should I go to the trouble of saying “GNU/"
@@ -1466,6 +1482,39 @@
"razloga</a>."
#. type: Content of: <dl><dt>
+# | [-Why do you write “GNU/Linux” instead-]{+How about calling
+# | the system “GliNUx” (instead+} of [-“GNU Linux”?-]
+# | {+“GNU/Linux”)?+} <span class=\"anchor-reference-id\">(<a
+# | [-href=\"#whyslash\">#whyslash</a>)</span>-]
+# | {+href=\"#long1\">#long1</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Why do you write “GNU/Linux” instead of “GNU "
+#| "Linux”? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+#| "\">#whyslash</a>)</span>"
+msgid ""
+"How about calling the system “GliNUx” (instead of “GNU/"
+"Linux”)? <span class=\"anchor-reference-id\">(<a href="
+"\"#long1\">#long1</a>)</span>"
+msgstr ""
+"ZaÅ¡to piÅ¡ete “GNU/Linux” umjesto “GNU Linux”? <span
"
+"class=\"anchor-reference-id\">(<a href=\"#whyslash\">#whyslash</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The name “GNU” does not visibly appear in “Glinux,” "
+"so most people would not notice it is there. Even if it is capitalized as "
+"“GliNUx,” most people would not realize that it contains a "
+"reference to GNU."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It would be comparable to writing “GNU/Linux,” but putting "
+"“GNU/” in print so small that most people could not read it."
+msgstr ""
+
+#. type: Content of: <dl><dt>
msgid ""
"The problem with “GNU/Linux” is that it is too long. Why should "
"I go to the trouble of saying “GNU/”? <span class=\"anchor-"
Index: gnu-linux-faq.it.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.it.po,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- gnu-linux-faq.it.po 18 Aug 2016 17:00:15 -0000 1.24
+++ gnu-linux-faq.it.po 18 Aug 2016 20:28:26 -0000 1.25
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2016-08-18 16:55+0000\n"
+"POT-Creation-Date: 2016-08-18 20:25+0000\n"
"PO-Revision-Date: 2015-12-14 23:30+0100\n"
"Last-Translator: Andrea Pescetti <address@hidden>\n"
"Language-Team: Italian <address@hidden>\n"
@@ -212,6 +212,22 @@
"che è troppo lungo. Perché non cercare un nome più corto?</a>"
#. type: Content of: <ul><li>
+# | <a [-href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write
+# | “GNU/Linux” instead-] {+href=\"#long1\" id=\"TOClong1\">How
+# | about calling the system “GliNUx” (instead+} of [-“GNU
+# | Linux”?</a>-] {+“GNU/Linux”)?</a>+}
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write “GNU/"
+#| "Linux” instead of “GNU Linux”?</a>"
+msgid ""
+"<a href=\"#long1\" id=\"TOClong1\">How about calling the system “"
+"GliNUx” (instead of “GNU/Linux”)?</a>"
+msgstr ""
+"<a href=\"#whyslash\" id=\"TOCwhyslash\">Perché scrivete “GNU/"
+"Linux” al posto di “GNU Linux”?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#long2\" id=\"TOClong2\">The problem with “GNU/Linux” "
"is that it is too long. Why should I go to the trouble of saying “GNU/"
@@ -1476,6 +1492,40 @@
"descritte</a>"
#. type: Content of: <dl><dt>
+# | [-Why do you write “GNU/Linux” instead-]{+How about calling
+# | the system “GliNUx” (instead+} of [-“GNU Linux”?-]
+# | {+“GNU/Linux”)?+} <span class=\"anchor-reference-id\">(<a
+# | [-href=\"#whyslash\">#whyslash</a>)</span>-]
+# | {+href=\"#long1\">#long1</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Why do you write “GNU/Linux” instead of “GNU "
+#| "Linux”? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+#| "\">#whyslash</a>)</span>"
+msgid ""
+"How about calling the system “GliNUx” (instead of “GNU/"
+"Linux”)? <span class=\"anchor-reference-id\">(<a href="
+"\"#long1\">#long1</a>)</span>"
+msgstr ""
+"Perché scrivete “GNU/Linux” al posto di “GNU Linux”?
"
+"<span class=\"anchor-reference-id\">(<a href=\"#whyslash\">#whyslash</a>)</"
+"span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The name “GNU” does not visibly appear in “Glinux,” "
+"so most people would not notice it is there. Even if it is capitalized as "
+"“GliNUx,” most people would not realize that it contains a "
+"reference to GNU."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It would be comparable to writing “GNU/Linux,” but putting "
+"“GNU/” in print so small that most people could not read it."
+msgstr ""
+
+#. type: Content of: <dl><dt>
msgid ""
"The problem with “GNU/Linux” is that it is too long. Why should "
"I go to the trouble of saying “GNU/”? <span class=\"anchor-"
Index: gnu-linux-faq.ja.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.ja.po,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -b -r1.65 -r1.66
--- gnu-linux-faq.ja.po 18 Aug 2016 17:00:16 -0000 1.65
+++ gnu-linux-faq.ja.po 18 Aug 2016 20:28:26 -0000 1.66
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2016-08-18 16:55+0000\n"
+"POT-Creation-Date: 2016-08-18 20:25+0000\n"
"PO-Revision-Date: 2015-12-29 14:23+0900\n"
"Last-Translator: NIIBE Yutaka <address@hidden>\n"
"Language-Team: Japanese <address@hidden>\n"
@@ -208,6 +208,18 @@
"ã¨ã§ãããã£ã¨çãååãæ¨å¥¨ã§ãã¾ããã?</a>"
#. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write “GNU/"
+#| "Linux” instead of “GNU Linux”?</a>"
+msgid ""
+"<a href=\"#long1\" id=\"TOClong1\">How about calling the system “"
+"GliNUx” (instead of “GNU/Linux”)?</a>"
+msgstr ""
+"<a href=\"#whyslash\"
id=\"TOCwhyslash\">ãªãã“GNU/Linux”ã¨æ¸ã"
+"ã®ã§ãããã“GNU Linux”ã§ã¯ãªãã¦?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#long2\" id=\"TOClong2\">The problem with “GNU/Linux” "
"is that it is too long. Why should I go to the trouble of saying “GNU/"
@@ -1439,6 +1451,35 @@
"\">ä¸è¨ã«ç¤ºãçç±</a>ã«ãããããããã¡ã¯“GNU/Linux”ã¨å¼ã³ã¾ãã"
#. type: Content of: <dl><dt>
+#, fuzzy
+#| msgid ""
+#| "Why do you write “GNU/Linux” instead of “GNU "
+#| "Linux”? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+#| "\">#whyslash</a>)</span>"
+msgid ""
+"How about calling the system “GliNUx” (instead of “GNU/"
+"Linux”)? <span class=\"anchor-reference-id\">(<a href="
+"\"#long1\">#long1</a>)</span>"
+msgstr ""
+"ãªãã“GNU/Linux”ã¨æ¸ãã®ã§ãããã“GNU
Linux”ã§ã¯ãª"
+"ãã¦?<span class=\"anchor-reference-id\">(<a href=\"#whyslash\">#whyslash</"
+"a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The name “GNU” does not visibly appear in “Glinux,” "
+"so most people would not notice it is there. Even if it is capitalized as "
+"“GliNUx,” most people would not realize that it contains a "
+"reference to GNU."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It would be comparable to writing “GNU/Linux,” but putting "
+"“GNU/” in print so small that most people could not read it."
+msgstr ""
+
+#. type: Content of: <dl><dt>
msgid ""
"The problem with “GNU/Linux” is that it is too long. Why should "
"I go to the trouble of saying “GNU/”? <span class=\"anchor-"
Index: gnu-linux-faq.ko.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.ko.po,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- gnu-linux-faq.ko.po 18 Aug 2016 17:00:16 -0000 1.13
+++ gnu-linux-faq.ko.po 18 Aug 2016 20:28:26 -0000 1.14
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2016-08-18 16:55+0000\n"
+"POT-Creation-Date: 2016-08-18 20:25+0000\n"
"PO-Revision-Date: 2016-05-21 13:58+0900\n"
"Last-Translator: Jongmin Yoon <address@hidden>\n"
"Language-Team: Korean <address@hidden>\n"
@@ -203,6 +203,18 @@
"ë ê±°ìì. 짧ì ì´ë¦ì ì¶ì²í´ 주ë ê² ì´ëì?</a>"
#. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write “GNU/"
+#| "Linux” instead of “GNU Linux”?</a>"
+msgid ""
+"<a href=\"#long1\" id=\"TOClong1\">How about calling the system “"
+"GliNUx” (instead of “GNU/Linux”)?</a>"
+msgstr ""
+"<a href=\"#whyslash\" id=\"TOCwhyslash\">ì “GNU Linux”ëì "
+"“GNU/Linux”ë¼ê³ ì°ëì?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#long2\" id=\"TOClong2\">The problem with “GNU/Linux” "
"is that it is too long. Why should I go to the trouble of saying “GNU/"
@@ -1407,6 +1419,34 @@
"ì ì´ì ë¡ “GNU/Linux”ë¼ ë¶ë¦
ëë¤."
#. type: Content of: <dl><dt>
+#, fuzzy
+#| msgid ""
+#| "Why do you write “GNU/Linux” instead of “GNU "
+#| "Linux”? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+#| "\">#whyslash</a>)</span>"
+msgid ""
+"How about calling the system “GliNUx” (instead of “GNU/"
+"Linux”)? <span class=\"anchor-reference-id\">(<a href="
+"\"#long1\">#long1</a>)</span>"
+msgstr ""
+"ì “GNU Linux”ëì “GNU/Linux”ë¼ê³
ì°ëì?<span "
+"class=\"anchor-reference-id\">(<a href=\"#whyslash\">#whyslash</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The name “GNU” does not visibly appear in “Glinux,” "
+"so most people would not notice it is there. Even if it is capitalized as "
+"“GliNUx,” most people would not realize that it contains a "
+"reference to GNU."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It would be comparable to writing “GNU/Linux,” but putting "
+"“GNU/” in print so small that most people could not read it."
+msgstr ""
+
+#. type: Content of: <dl><dt>
msgid ""
"The problem with “GNU/Linux” is that it is too long. Why should "
"I go to the trouble of saying “GNU/”? <span class=\"anchor-"
Index: gnu-linux-faq.nl-diff.html
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.nl-diff.html,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -b -r1.34 -r1.35
--- gnu-linux-faq.nl-diff.html 18 Aug 2016 17:00:16 -0000 1.34
+++ gnu-linux-faq.nl-diff.html 18 Aug 2016 20:28:26 -0000 1.35
@@ -11,7 +11,7 @@
</style></head>
<body><pre>
<!--#include virtual="/server/header.html" -->
-<span class="inserted"><ins><em><!-- Parent-Version: 1.77
--></em></ins></span>
+<span class="inserted"><ins><em><!-- Parent-Version: 1.79
--></em></ins></span>
<title>GNU/Linux FAQ
- GNU Project - Free Software <span class="removed"><del><strong>Foundation
(FSF)</title></strong></del></span> <span
class="inserted"><ins><em>Foundation</title></em></ins></span>
<!--#include <span
class="removed"><del><strong>virtual="/server/banner.html"</strong></del></span>
<span
class="inserted"><ins><em>virtual="/gnu/po/gnu-linux-faq.translist"</em></ins></span>
-->
@@ -96,7 +96,10 @@
“GNU/Linux” is that it is too long. How about
recommending a shorter name?</a></li>
-<li><a <span class="inserted"><ins><em>href="#long2"
id="TOClong2">The problem with
+<li><a <span class="inserted"><ins><em>href="#long1"
id="TOClong1">How about calling the system
+ “GliNUx” (instead of
“GNU/Linux”)?</a></li>
+
+<li><a href="#long2" id="TOClong2">The problem with
“GNU/Linux” is that it is too long. Why should
I go to the trouble of saying “GNU/”?</a></li>
@@ -589,9 +592,9 @@
We expected to release</em></ins></span> the <span
class="inserted"><ins><em>GNU</em></ins></span> system <span
class="removed"><del><strong>as</strong></del></span> <span
class="inserted"><ins><em>packaged for installation, but
this plan was overtaken by events: in 1992 others were already
packaging GNU variants containing Linux. Starting in 1993 we
-sponsored an effort to make</em></ins></span> a <span
class="removed"><del><strong>whole.</strong></del></span> <span
class="inserted"><ins><em>better and freer GNU/Linux distribution,
+sponsored an effort to make</em></ins></span> a <span
class="removed"><del><strong>whole. The kernel</strong></del></span> <span
class="inserted"><ins><em>better and freer GNU/Linux distribution,
called <a href="/distros/common-distros.html#Debian">Debian
-GNU/Linux</a>.</em></ins></span> The <span
class="removed"><del><strong>kernel usually</strong></del></span> <span
class="inserted"><ins><em>founder of Debian had already chosen that name.
+GNU/Linux</a>. The founder of Debian had already chosen that name.
We did not ask him to call it just “GNU” because that was
to be the name of a system version with the GNU Hurd kernel—which
wasn't ready yet.</p>
@@ -622,7 +625,7 @@
That practice seems to be very rare—we can't find any examples other
than the misuse of the name “Linux”. Normally an operating system
is
developed as a single unified project, and the developers choose a
-name for the system as a whole. The kernel usually</em></ins></span> does not
have a
+name for the system as a whole. The kernel</em></ins></span> usually does not
have a
name of its own—instead, people say “the kernel of
such-and-such” or
“the such-and-such kernel”.
<p>
@@ -657,9 +660,24 @@
given <span
class="removed"><del><strong>below.</p></strong></del></span> <span
class="inserted"><ins><em>below</a>.</p></em></ins></span>
</dd>
-<dt <span class="removed"><del><strong>id="justgnu">Since
Linux</strong></del></span> <span class="inserted"><ins><em>id="long2">The
problem with “GNU/Linux”</em></ins></span> is <span
class="removed"><del><strong>a secondary
- contribution, would</strong></del></span> <span
class="inserted"><ins><em>that</em></ins></span> it <span
class="removed"><del><strong>be false</strong></del></span> <span
class="inserted"><ins><em>is too long.
- Why should I go</em></ins></span> to the <span
class="removed"><del><strong>facts</strong></del></span> <span
class="inserted"><ins><em>trouble of saying “GNU/”?
+<dt <span class="removed"><del><strong>id="justgnu">Since Linux is a
secondary
+ contribution, would it be false to</strong></del></span> <span
class="inserted"><ins><em>id="long1">How about calling</em></ins></span> the
<span class="removed"><del><strong>facts</strong></del></span> <span
class="inserted"><ins><em>system
+ “GliNUx” (instead of “GNU/Linux”)?
+ <span class="anchor-reference-id">(<a
href="#long1">#long1</a>)</span></dt>
+
+<dd>
+<p>The name “GNU” does not visibly appear in
+“Glinux,” so most people would not notice it is there.
+Even if it is capitalized as “GliNUx,” most people would
+not realize that it contains a reference to GNU.</p>
+
+<p>It would be comparable to writing “GNU/Linux,” but
+putting “GNU/” in print so small that most people could
+not read it.</p>
+</dd>
+
+<dt id="long2">The problem with “GNU/Linux” is that it is
too long.
+ Why should I go to the trouble of saying “GNU/”?
<span class="anchor-reference-id">(<a
href="#long2">#long2</a>)</span></dt>
<dd>
@@ -1174,10 +1192,12 @@
<dd>
There are complete systems that contain Linux and not GNU; Android is
an example. But it is a mistake to call them “Linux”
-<span class="removed"><del><strong>systems.</strong></del></span>
-<span class="inserted"><ins><em>systems, just as it is a mistake to call GNU a
“Linux” system.</em></ins></span>
+<span class="removed"><del><strong>systems.
+<p>
+Android</strong></del></span>
+<span class="inserted"><ins><em>systems, just as it</em></ins></span> is <span
class="removed"><del><strong>very different from</strong></del></span> <span
class="inserted"><ins><em>a mistake to call GNU a “Linux” system.
<p>
-Android is very different from the GNU/Linux system—because <span
class="removed"><del><strong>it
+Android is very different from</em></ins></span> the GNU/Linux
system—because <span class="removed"><del><strong>it
contains</strong></del></span>
<span class="inserted"><ins><em>the two have</em></ins></span> very little
<span class="removed"><del><strong>of</strong></del></span> <span
class="inserted"><ins><em>code in common. In fact,</em></ins></span> the <span
class="removed"><del><strong>GNU system,</strong></del></span> only <span
class="removed"><del><strong>Linux. Overall, it's a
different system.</strong></del></span> <span class="inserted"><ins><em>thing
they
@@ -1189,35 +1209,34 @@
[sic] libraries and utilities [meaning the GNU <span
class="removed"><del><strong>system].”</strong></del></span> <span
class="inserted"><ins><em>system].”</p>
<p></em></ins></span>
Android contains just as much of Linux as GNU/Linux does. What it
-doesn't have is the GNU system. <span class="removed"><del><strong>Instead it
has a lot of</strong></del></span> <span class="inserted"><ins><em>Android
replaces that with</em></ins></span> Google <span
class="removed"><del><strong>software.</p></strong></del></span>
-<span class="inserted"><ins><em>software that works quite differently. What
makes Android different
-from GNU/Linux is the absence of GNU.</p></em></ins></span>
+doesn't have is the GNU system. <span class="removed"><del><strong>Instead it
has</strong></del></span> <span class="inserted"><ins><em>Android replaces
that with Google
+software that works quite differently. What makes Android different
+from GNU/Linux is the absence of GNU.</p>
</dd>
-<dt <span class="removed"><del><strong>id="helplinus">Why not
call</strong></del></span> <span class="inserted"><ins><em>id="howmuch">How
much of</em></ins></span> the <span
class="inserted"><ins><em>GNU</em></ins></span> system
- <span class="removed"><del><strong>“Linux” anyway, and
strengthen Linus Torvalds' role as posterboy</strong></del></span> <span
class="inserted"><ins><em>is needed</em></ins></span> for <span
class="removed"><del><strong>our</strong></del></span> <span
class="inserted"><ins><em>the system
+<dt id="howmuch">How much of the GNU system is needed for the system
to be
GNU/Linux? <span class="anchor-reference-id">(<a
href="#howmuch">#howmuch</a>)</span></dt>
<dd>
-“How much” is not a meaningful question because the GNU
+“How much” is not</em></ins></span> a <span
class="removed"><del><strong>lot</strong></del></span> <span
class="inserted"><ins><em>meaningful question because the GNU
system does not have precise boundaries.
<p>
GNU is an operating system maintained by a community. It includes far
more than just the GNU software packages (of which we have a specific
list), and people add more packages constantly. Despite these
changes, it remains the GNU system, and adding Linux to that yields
-GNU/Linux. If you use part of the GNU system and omit part, there is
+GNU/Linux. If you use part</em></ins></span> of <span
class="removed"><del><strong>Google software.</p></strong></del></span>
<span class="inserted"><ins><em>the GNU system and omit part, there is
no meaningful way to say “how much” you used.</p>
<p>
If we look at the level of packages, Linux is one important package in
the GNU/Linux system. The inclusion of one important GNU package is
enough to justify our request for equal mention.
-</p>
+</p></em></ins></span>
</dd>
<dt id="helplinus">Why not call the system
- “Linux” anyway, and strengthen Linus Torvalds' role as
posterboy for our</em></ins></span>
+ “Linux” anyway, and strengthen Linus Torvalds' role as
posterboy for our
community? <span class="anchor-reference-id">(<a
href="#helplinus">#helplinus</a>)</span></dt>
<dd>
@@ -1428,12 +1447,13 @@
It would be hypocritical to make the name GNU/Linux a license
requirement, and we don't. We only <em>ask</em> you to give us the
credit we deserve.
+<span class="removed"><del><strong></dd></strong></del></span>
<span class="inserted"><ins><em><p>
Please note that there are at least <a href="/licenses/bsd.html">
two different BSD licenses</a>. For clarity's sake, please don't use
-the term “BSD license” without specifying which
one.</p></em></ins></span>
-</dd>
+the term “BSD license” without specifying which one.</p>
+</dd></em></ins></span>
<dt id="deserve">Since you failed to put
something in the GNU GPL to require people to call the system
“GNU”,
@@ -1468,21 +1488,19 @@
We don't think that the popularity of an error makes it the truth.
</dd>
-<dt <span class="removed"><del><strong>id="winning">Many people care
about what's
- convenient or who's winning,</strong></del></span> <span
class="inserted"><ins><em>id="knownname">Isn't it better to call the
+<dt <span class="inserted"><ins><em>id="knownname">Isn't it better to
call the
system by the name most users already know? <span
class="anchor-reference-id">(<a
href="#knownname">#knownname</a>)</span></dt>
<dd>
-Users are</em></ins></span> not <span class="removed"><del><strong>about
arguments</strong></del></span> <span
class="inserted"><ins><em>incapable</em></ins></span> of <span
class="removed"><del><strong>right or wrong.
- Couldn't you get</strong></del></span> <span
class="inserted"><ins><em>learning. Since “GNU/Linux”
+Users are not incapable of learning. Since “GNU/Linux”
includes “Linux”, they will recognize what you're talking
about. If you add “(often erroneously referred to as
‘Linux’)” once in a while, they will all understand.
</dd>
-<dt id="winning">Many people care about what's
+<dt</em></ins></span> id="winning">Many people care about what's
convenient or who's winning, not about arguments of right or wrong.
- Couldn't you get</em></ins></span> more of their support by a different
+ Couldn't you get more of their support by a different
road? <span class="anchor-reference-id">(<a
href="#winning">#winning</a>)</span></dt>
<dd>
@@ -1554,7 +1572,7 @@
Either "2001, 2002, 2003"</em></ins></span> or <span
class="removed"><del><strong>WEBLANG -->
<!-- -</strong></del></span> <span class="inserted"><ins><em>"2001-2003"
are ok for specifying
years, as long as each year</em></ins></span> in <span
class="removed"><del><strong>/home/www/html/server/standards/README.translations.html
-->
-<!-- one of</strong></del></span> the <span
class="removed"><del><strong>lists under the section "Translations Underway"
-->
+<!-- one of the lists under</strong></del></span> the <span
class="removed"><del><strong>section "Translations Underway" -->
<!-- - if there</strong></del></span> <span
class="inserted"><ins><em>range</em></ins></span> is <span
class="inserted"><ins><em>in fact</em></ins></span> a <span
class="removed"><del><strong>translation team, you also have to add an alias
-->
<!-- to mail.gnu.org:/com/mailer/aliases -->
<!-- Please also check you have</strong></del></span> <span
class="inserted"><ins><em>copyrightable
@@ -1598,7 +1616,7 @@
<p class="unprintable">Updated:</em></ins></span>
<!-- timestamp start -->
-$Date: 2016/08/18 17:00:16 $
+$Date: 2016/08/18 20:28:26 $
<!-- timestamp end -->
</p>
</div>
Index: gnu-linux-faq.nl.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.nl.po,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -b -r1.39 -r1.40
--- gnu-linux-faq.nl.po 18 Aug 2016 17:00:16 -0000 1.39
+++ gnu-linux-faq.nl.po 18 Aug 2016 20:28:26 -0000 1.40
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2016-08-18 16:55+0000\n"
+"POT-Creation-Date: 2016-08-18 20:25+0000\n"
"PO-Revision-Date: \n"
"Last-Translator: Tom Uijldert <address@hidden>\n"
"Language-Team: Dutch\n"
@@ -207,6 +207,22 @@
"dat het te lang is. Heb je niet iets korters?</a>"
#. type: Content of: <ul><li>
+# | <a [-href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write
+# | “GNU/Linux” instead-] {+href=\"#long1\" id=\"TOClong1\">How
+# | about calling the system “GliNUx” (instead+} of [-“GNU
+# | Linux”?</a>-] {+“GNU/Linux”)?</a>+}
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write “GNU/"
+#| "Linux” instead of “GNU Linux”?</a>"
+msgid ""
+"<a href=\"#long1\" id=\"TOClong1\">How about calling the system “"
+"GliNUx” (instead of “GNU/Linux”)?</a>"
+msgstr ""
+"<a href=\"#whyslash\" id=\"TOCwhyslash\">Waarom spel je het “GNU/"
+"Linux” in plaats van “GNU Linux”?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#long2\" id=\"TOClong2\">The problem with “GNU/Linux” "
"is that it is too long. Why should I go to the trouble of saying “GNU/"
@@ -1445,6 +1461,40 @@
"antwoord voor het waarom</a>."
#. type: Content of: <dl><dt>
+# | [-Why do you write “GNU/Linux” instead-]{+How about calling
+# | the system “GliNUx” (instead+} of [-“GNU Linux”?-]
+# | {+“GNU/Linux”)?+} <span class=\"anchor-reference-id\">(<a
+# | [-href=\"#whyslash\">#whyslash</a>)</span>-]
+# | {+href=\"#long1\">#long1</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Why do you write “GNU/Linux” instead of “GNU "
+#| "Linux”? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+#| "\">#whyslash</a>)</span>"
+msgid ""
+"How about calling the system “GliNUx” (instead of “GNU/"
+"Linux”)? <span class=\"anchor-reference-id\">(<a href="
+"\"#long1\">#long1</a>)</span>"
+msgstr ""
+"Waarom spel je het “GNU/Linux” in plaats van “GNU "
+"Linux”? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+"\">#whyslash</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The name “GNU” does not visibly appear in “Glinux,” "
+"so most people would not notice it is there. Even if it is capitalized as "
+"“GliNUx,” most people would not realize that it contains a "
+"reference to GNU."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It would be comparable to writing “GNU/Linux,” but putting "
+"“GNU/” in print so small that most people could not read it."
+msgstr ""
+
+#. type: Content of: <dl><dt>
msgid ""
"The problem with “GNU/Linux” is that it is too long. Why should "
"I go to the trouble of saying “GNU/”? <span class=\"anchor-"
Index: gnu-linux-faq.pl.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.pl.po,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -b -r1.69 -r1.70
--- gnu-linux-faq.pl.po 18 Aug 2016 17:00:16 -0000 1.69
+++ gnu-linux-faq.pl.po 18 Aug 2016 20:28:26 -0000 1.70
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2016-08-18 16:55+0000\n"
+"POT-Creation-Date: 2016-08-18 20:25+0000\n"
"PO-Revision-Date: 2016-02-16 21:20-0600\n"
"Last-Translator: Jan Owoc <jsowoc AT gmail.com>\n"
"Language-Team: Polish <address@hidden>\n"
@@ -215,6 +215,22 @@
"kÅopot, bo jest za dÅuga. Może zaproponujecie krótszÄ
nazwÄ?</a>"
#. type: Content of: <ul><li>
+# | <a [-href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write
+# | “GNU/Linux” instead-] {+href=\"#long1\" id=\"TOClong1\">How
+# | about calling the system “GliNUx” (instead+} of [-“GNU
+# | Linux”?</a>-] {+“GNU/Linux”)?</a>+}
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write “GNU/"
+#| "Linux” instead of “GNU Linux”?</a>"
+msgid ""
+"<a href=\"#long1\" id=\"TOClong1\">How about calling the system “"
+"GliNUx” (instead of “GNU/Linux”)?</a>"
+msgstr ""
+"<a href=\"#whyslash\" id=\"TOCwhyslash\">Czemu piszecie „GNU/"
+"Linux” zamiast „GNU Linux”?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#long2\" id=\"TOClong2\">The problem with “GNU/Linux” "
"is that it is too long. Why should I go to the trouble of saying “GNU/"
@@ -1500,6 +1516,40 @@
"\"#justgnu\">z powodów podanych poniżej</a>."
#. type: Content of: <dl><dt>
+# | [-Why do you write “GNU/Linux” instead-]{+How about calling
+# | the system “GliNUx” (instead+} of [-“GNU Linux”?-]
+# | {+“GNU/Linux”)?+} <span class=\"anchor-reference-id\">(<a
+# | [-href=\"#whyslash\">#whyslash</a>)</span>-]
+# | {+href=\"#long1\">#long1</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Why do you write “GNU/Linux” instead of “GNU "
+#| "Linux”? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+#| "\">#whyslash</a>)</span>"
+msgid ""
+"How about calling the system “GliNUx” (instead of “GNU/"
+"Linux”)? <span class=\"anchor-reference-id\">(<a href="
+"\"#long1\">#long1</a>)</span>"
+msgstr ""
+"Czemu piszecie „GNU/Linux” zamiast „GNU Linux”? "
+"<span class=\"anchor-reference-id\">(<a href=\"#whyslash\">#whyslash</a>)</"
+"span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The name “GNU” does not visibly appear in “Glinux,” "
+"so most people would not notice it is there. Even if it is capitalized as "
+"“GliNUx,” most people would not realize that it contains a "
+"reference to GNU."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It would be comparable to writing “GNU/Linux,” but putting "
+"“GNU/” in print so small that most people could not read it."
+msgstr ""
+
+#. type: Content of: <dl><dt>
msgid ""
"The problem with “GNU/Linux” is that it is too long. Why should "
"I go to the trouble of saying “GNU/”? <span class=\"anchor-"
Index: gnu-linux-faq.pot
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.pot,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -b -r1.43 -r1.44
--- gnu-linux-faq.pot 18 Aug 2016 17:00:16 -0000 1.43
+++ gnu-linux-faq.pot 18 Aug 2016 20:28:26 -0000 1.44
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2016-08-18 16:55+0000\n"
+"POT-Creation-Date: 2016-08-18 20:25+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"
@@ -160,6 +160,12 @@
#. type: Content of: <ul><li>
msgid ""
+"<a href=\"#long1\" id=\"TOClong1\">How about calling the system "
+"“GliNUx” (instead of “GNU/Linux”)?</a>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
"<a href=\"#long2\" id=\"TOClong2\">The problem with “GNU/Linux” "
"is that it is too long. Why should I go to the trouble of saying "
"“GNU/”?</a>"
@@ -1007,6 +1013,27 @@
#. type: Content of: <dl><dt>
msgid ""
+"How about calling the system “GliNUx” (instead of "
+"“GNU/Linux”)? <span class=\"anchor-reference-id\">(<a "
+"href=\"#long1\">#long1</a>)</span>"
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The name “GNU” does not visibly appear in “Glinux,” "
+"so most people would not notice it is there. Even if it is capitalized as "
+"“GliNUx,” most people would not realize that it contains a "
+"reference to GNU."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It would be comparable to writing “GNU/Linux,” but putting "
+"“GNU/” in print so small that most people could not read it."
+msgstr ""
+
+#. type: Content of: <dl><dt>
+msgid ""
"The problem with “GNU/Linux” is that it is too long. Why should "
"I go to the trouble of saying “GNU/”? <span "
"class=\"anchor-reference-id\">(<a href=\"#long2\">#long2</a>)</span>"
Index: gnu-linux-faq.ru.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.ru.po,v
retrieving revision 1.82
retrieving revision 1.83
diff -u -b -r1.82 -r1.83
--- gnu-linux-faq.ru.po 18 Aug 2016 17:00:16 -0000 1.82
+++ gnu-linux-faq.ru.po 18 Aug 2016 20:28:26 -0000 1.83
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2016-08-18 16:55+0000\n"
+"POT-Creation-Date: 2016-08-18 20:25+0000\n"
"PO-Revision-Date: 2015-12-14 17:17+0000\n"
"Last-Translator: Ineiev <address@hidden>\n"
"Language-Team: Russian <address@hidden>\n"
@@ -239,6 +239,23 @@
# type: Content of: <ul><li>
#. type: Content of: <ul><li>
+# | <a [-href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write
+# | “GNU/Linux” instead-] {+href=\"#long1\" id=\"TOClong1\">How
+# | about calling the system “GliNUx” (instead+} of [-“GNU
+# | Linux”?</a>-] {+“GNU/Linux”)?</a>+}
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write “GNU/"
+#| "Linux” instead of “GNU Linux”?</a>"
+msgid ""
+"<a href=\"#long1\" id=\"TOClong1\">How about calling the system “"
+"GliNUx” (instead of “GNU/Linux”)?</a>"
+msgstr ""
+"<a href=\"#whyslash\" id=\"TOCwhyslash\">ÐоÑÐµÐ¼Ñ Ð²Ñ Ð¿Ð¸ÑеÑе
“GNU/"
+"Linux” вмеÑÑо “GNU Linux”?</a>"
+
+# type: Content of: <ul><li>
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#long2\" id=\"TOClong2\">The problem with “GNU/Linux” "
"is that it is too long. Why should I go to the trouble of saying “GNU/"
@@ -1613,6 +1630,41 @@
# type: Content of: <dl><dt>
#. type: Content of: <dl><dt>
+# | [-Why do you write “GNU/Linux” instead-]{+How about calling
+# | the system “GliNUx” (instead+} of [-“GNU Linux”?-]
+# | {+“GNU/Linux”)?+} <span class=\"anchor-reference-id\">(<a
+# | [-href=\"#whyslash\">#whyslash</a>)</span>-]
+# | {+href=\"#long1\">#long1</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Why do you write “GNU/Linux” instead of “GNU "
+#| "Linux”? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+#| "\">#whyslash</a>)</span>"
+msgid ""
+"How about calling the system “GliNUx” (instead of “GNU/"
+"Linux”)? <span class=\"anchor-reference-id\">(<a href="
+"\"#long1\">#long1</a>)</span>"
+msgstr ""
+"ÐоÑÐµÐ¼Ñ Ð²Ñ Ð¿Ð¸ÑеÑе “GNU/Linux” вмеÑÑо
“GNU Linux”? "
+"<span class=\"anchor-reference-id\">(<a href=\"#whyslash\">#whyslash</a>)</"
+"span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The name “GNU” does not visibly appear in “Glinux,” "
+"so most people would not notice it is there. Even if it is capitalized as "
+"“GliNUx,” most people would not realize that it contains a "
+"reference to GNU."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It would be comparable to writing “GNU/Linux,” but putting "
+"“GNU/” in print so small that most people could not read it."
+msgstr ""
+
+# type: Content of: <dl><dt>
+#. type: Content of: <dl><dt>
msgid ""
"The problem with “GNU/Linux” is that it is too long. Why should "
"I go to the trouble of saying “GNU/”? <span class=\"anchor-"
Index: gnu-linux-faq.sq.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.sq.po,v
retrieving revision 1.84
retrieving revision 1.85
diff -u -b -r1.84 -r1.85
--- gnu-linux-faq.sq.po 18 Aug 2016 17:00:17 -0000 1.84
+++ gnu-linux-faq.sq.po 18 Aug 2016 20:28:26 -0000 1.85
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: gnu-linux-faq.html\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2016-08-18 16:55+0000\n"
+"POT-Creation-Date: 2016-08-18 20:25+0000\n"
"PO-Revision-Date: 2016-01-02 18:52+0200\n"
"Last-Translator: Besnik Bleta <address@hidden>\n"
"Language-Team: sq\n"
@@ -209,6 +209,18 @@
"është shumë i gjatë. Po sikur të këshillonit një emër më të
shkurtër?</a>"
#. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write “GNU/"
+#| "Linux” instead of “GNU Linux”?</a>"
+msgid ""
+"<a href=\"#long1\" id=\"TOClong1\">How about calling the system “"
+"GliNUx” (instead of “GNU/Linux”)?</a>"
+msgstr ""
+"<a href=\"#whyslash\" id=\"TOCwhyslash\">Pse e shkruani “GNU/"
+"Linux” në vend se “GNU Linux”?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#long2\" id=\"TOClong2\">The problem with “GNU/Linux” "
"is that it is too long. Why should I go to the trouble of saying “GNU/"
@@ -1460,6 +1472,35 @@
"poshtë</a>."
#. type: Content of: <dl><dt>
+#, fuzzy
+#| msgid ""
+#| "Why do you write “GNU/Linux” instead of “GNU "
+#| "Linux”? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+#| "\">#whyslash</a>)</span>"
+msgid ""
+"How about calling the system “GliNUx” (instead of “GNU/"
+"Linux”)? <span class=\"anchor-reference-id\">(<a href="
+"\"#long1\">#long1</a>)</span>"
+msgstr ""
+"Pse e shkruani “GNU/Linux” në vend se “GNU Linux”? "
+"<span class=\"anchor-reference-id\">(<a href=\"#whyslash\">#whyslash</a>)</"
+"span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The name “GNU” does not visibly appear in “Glinux,” "
+"so most people would not notice it is there. Even if it is capitalized as "
+"“GliNUx,” most people would not realize that it contains a "
+"reference to GNU."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It would be comparable to writing “GNU/Linux,” but putting "
+"“GNU/” in print so small that most people could not read it."
+msgstr ""
+
+#. type: Content of: <dl><dt>
msgid ""
"The problem with “GNU/Linux” is that it is too long. Why should "
"I go to the trouble of saying “GNU/”? <span class=\"anchor-"
Index: gnu-linux-faq.sr.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.sr.po,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -b -r1.46 -r1.47
--- gnu-linux-faq.sr.po 18 Aug 2016 17:00:17 -0000 1.46
+++ gnu-linux-faq.sr.po 18 Aug 2016 20:28:26 -0000 1.47
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2016-08-18 16:55+0000\n"
+"POT-Creation-Date: 2016-08-18 20:25+0000\n"
"PO-Revision-Date: 2008-07-25 13:26+0200\n"
"Last-Translator: Strahinya Radich <address@hidden>\n"
"Language-Team: Serbian <address@hidden>\n"
@@ -222,6 +222,19 @@
# type: Content of: <ul><li>
#. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write “GNU/"
+#| "Linux” instead of “GNU Linux”?</a>"
+msgid ""
+"<a href=\"#long1\" id=\"TOClong1\">How about calling the system “"
+"GliNUx” (instead of “GNU/Linux”)?</a>"
+msgstr ""
+"<a href=\"#whyslash\" id=\"TOCwhyslash\">ÐаÑÑо пиÑеÑе âÐÐУ
Ñа ÐинÑкÑомâ "
+"ÑмеÑÑо âÐÐУ ÐинÑкÑâ?</a>"
+
+# type: Content of: <ul><li>
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#long2\" id=\"TOClong2\">The problem with “GNU/Linux” "
"is that it is too long. Why should I go to the trouble of saying “GNU/"
@@ -1519,6 +1532,35 @@
# type: Content of: <dl><dt>
#. type: Content of: <dl><dt>
+#, fuzzy
+#| msgid ""
+#| "Why do you write “GNU/Linux” instead of “GNU "
+#| "Linux”? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+#| "\">#whyslash</a>)</span>"
+msgid ""
+"How about calling the system “GliNUx” (instead of “GNU/"
+"Linux”)? <span class=\"anchor-reference-id\">(<a href="
+"\"#long1\">#long1</a>)</span>"
+msgstr ""
+"ÐаÑÑо пиÑеÑе âÐÐУ Ñа ÐинÑкÑомâ ÑмеÑÑо
âÐÐУ ÐинÑкÑâ? <span class=\"anchor-"
+"reference-id\">(<a href=\"#whyslash\">#whyslash</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The name “GNU” does not visibly appear in “Glinux,” "
+"so most people would not notice it is there. Even if it is capitalized as "
+"“GliNUx,” most people would not realize that it contains a "
+"reference to GNU."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It would be comparable to writing “GNU/Linux,” but putting "
+"“GNU/” in print so small that most people could not read it."
+msgstr ""
+
+# type: Content of: <dl><dt>
+#. type: Content of: <dl><dt>
msgid ""
"The problem with “GNU/Linux” is that it is too long. Why should "
"I go to the trouble of saying “GNU/”? <span class=\"anchor-"
Index: gnu-linux-faq.tr.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.tr.po,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -b -r1.50 -r1.51
--- gnu-linux-faq.tr.po 18 Aug 2016 17:00:17 -0000 1.50
+++ gnu-linux-faq.tr.po 18 Aug 2016 20:28:26 -0000 1.51
@@ -11,7 +11,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2016-08-18 16:55+0000\n"
+"POT-Creation-Date: 2016-08-18 20:25+0000\n"
"PO-Revision-Date: 2010-01-07 13:09+0100\n"
"Last-Translator: Firat Ozgul <address@hidden>\n"
"Language-Team: Turkish <address@hidden>\n"
@@ -233,6 +233,19 @@
# type: Content of: <ul><li>
#. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write “GNU/"
+#| "Linux” instead of “GNU Linux”?</a>"
+msgid ""
+"<a href=\"#long1\" id=\"TOClong1\">How about calling the system “"
+"GliNUx” (instead of “GNU/Linux”)?</a>"
+msgstr ""
+"<a href=\"#whyslash\" id=\"TOCwhyslash\">Neden “GNU Linux” "
+"yerine “GNU/Linux” yazıyorsunuz?</a>"
+
+# type: Content of: <ul><li>
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#long2\" id=\"TOClong2\">The problem with “GNU/Linux” "
"is that it is too long. Why should I go to the trouble of saying “GNU/"
@@ -1565,6 +1578,36 @@
# type: Content of: <dl><dt>
#. type: Content of: <dl><dt>
+#, fuzzy
+#| msgid ""
+#| "Why do you write “GNU/Linux” instead of “GNU "
+#| "Linux”? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+#| "\">#whyslash</a>)</span>"
+msgid ""
+"How about calling the system “GliNUx” (instead of “GNU/"
+"Linux”)? <span class=\"anchor-reference-id\">(<a href="
+"\"#long1\">#long1</a>)</span>"
+msgstr ""
+"Neden “GNU Linux” yerine “GNU/Linux” yazıyorsunuz? "
+"<span class=\"anchor-reference-id\">(<a href=\"#whyslash\">#whyslash</a>)</"
+"span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The name “GNU” does not visibly appear in “Glinux,” "
+"so most people would not notice it is there. Even if it is capitalized as "
+"“GliNUx,” most people would not realize that it contains a "
+"reference to GNU."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It would be comparable to writing “GNU/Linux,” but putting "
+"“GNU/” in print so small that most people could not read it."
+msgstr ""
+
+# type: Content of: <dl><dt>
+#. type: Content of: <dl><dt>
msgid ""
"The problem with “GNU/Linux” is that it is too long. Why should "
"I go to the trouble of saying “GNU/”? <span class=\"anchor-"
Index: gnu-linux-faq.uk.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-linux-faq.uk.po,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- gnu-linux-faq.uk.po 18 Aug 2016 17:00:17 -0000 1.23
+++ gnu-linux-faq.uk.po 18 Aug 2016 20:28:27 -0000 1.24
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gnu-linux-faq.html\n"
-"POT-Creation-Date: 2016-08-18 16:55+0000\n"
+"POT-Creation-Date: 2016-08-18 20:25+0000\n"
"PO-Revision-Date: 2015-12-25 17:18+0200\n"
"Last-Translator: Andriy Bandura <address@hidden>\n"
"Language-Team: Ukrainian <>\n"
@@ -213,6 +213,18 @@
"a>"
#. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#whyslash\" id=\"TOCwhyslash\">Why do you write “GNU/"
+#| "Linux” instead of “GNU Linux”?</a>"
+msgid ""
+"<a href=\"#long1\" id=\"TOClong1\">How about calling the system “"
+"GliNUx” (instead of “GNU/Linux”)?</a>"
+msgstr ""
+"<a href=\"#whyslash\" id=\"TOCwhyslash\">Ð§Ð¾Ð¼Ñ Ð²Ð¸ пиÑеÑе
“GNU/"
+"Linux” замÑÑÑÑ “GNU Linux”?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#long2\" id=\"TOClong2\">The problem with “GNU/Linux” "
"is that it is too long. Why should I go to the trouble of saying “GNU/"
@@ -1463,6 +1475,35 @@
"пÑиÑин, викладениÑ
нижÑе</a>."
#. type: Content of: <dl><dt>
+#, fuzzy
+#| msgid ""
+#| "Why do you write “GNU/Linux” instead of “GNU "
+#| "Linux”? <span class=\"anchor-reference-id\">(<a href=\"#whyslash"
+#| "\">#whyslash</a>)</span>"
+msgid ""
+"How about calling the system “GliNUx” (instead of “GNU/"
+"Linux”)? <span class=\"anchor-reference-id\">(<a href="
+"\"#long1\">#long1</a>)</span>"
+msgstr ""
+"Ð§Ð¾Ð¼Ñ Ð²Ð¸ пиÑеÑе “GNU/Linux” замÑÑÑÑ “GNU
Ñ ÐС Linux”? "
+"<span class=\"anchor-reference-id\">(<a href=\"#whyslash\">#whyslash</a>)</"
+"span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"The name “GNU” does not visibly appear in “Glinux,” "
+"so most people would not notice it is there. Even if it is capitalized as "
+"“GliNUx,” most people would not realize that it contains a "
+"reference to GNU."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"It would be comparable to writing “GNU/Linux,” but putting "
+"“GNU/” in print so small that most people could not read it."
+msgstr ""
+
+#. type: Content of: <dl><dt>
msgid ""
"The problem with “GNU/Linux” is that it is too long. Why should "
"I go to the trouble of saying “GNU/”? <span class=\"anchor-"
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/gnu/po gnu-linux-faq.ar.po gnu-linux-faq.ca...,
GNUN <=