gnu-linux-faq.nl.po

Mismatched links: 31.

Mismatched ids: 0.

#text
22  
<a href="#nokernel">An operating system requires a kernel. Since the GNU Project didn't develop a kernel, how can the system be GNU?</a> 
 
30  
<a href="#long4">Stallman doesn't ask us to call him &ldquo;Richard Matthew Stallman&rdquo; every the time. So why ask us to say &ldquo;GNU/Linux&rdquo; every time?</a> 
 
34 | <a [-href="#manycompanies">Many companies contributed to-]
| {+href="#systemd">systemd plays an important role in+} the {+GNU/Linux+}
| system as it is today; [-doesn't that mean-] {+are+} we [-ought-]
| {+obligated+} to call it [-GNU/Red&nbsp;Hat/Novell/Linux?</a>-]
| {+GNU/systemd/Linux?</a>+} 
<a href="#systemd">systemd plays an important role in the GNU/Linux system as it is today; are we obligated to call it GNU/systemd/Linux?</a> 
<a href="#manycompanies">Veel bedrijven hebben bijgedragen aan het systeem zoals het nu is; betekent dat niet dat we het GNU/Redhat/Novell/Linux moeten noemen?</a> 
39 | <a [-href="#bsd">Should we say &ldquo;GNU/BSD&rdquo; too?</a>-]
| {+href="#pronounce">How is the name &ldquo;GNU/Linux&rdquo;
| pronounced?</a>+} 
<a href="#pronounce">How is the name &ldquo;GNU/Linux&rdquo; pronounced?</a> 
<a href="#bsd">Moeten we ook GNU/BSD zeggen?</a> 
40 | <a [-href="#whyslash">Why-] {+href="#whynoslash">Why+} do you write
| [-&ldquo;GNU/Linux&rdquo; instead of-] &ldquo;GNU [-Linux&rdquo;?</a>-]
| {+Emacs&rdquo; rather than &ldquo;GNU/Emacs&rdquo;?</a>+} 
<a href="#whynoslash">Why do you write &ldquo;GNU Emacs&rdquo; rather than &ldquo;GNU/Emacs&rdquo;?</a> 
<a href="#whyslash">Waarom spel je het &ldquo;GNU/Linux&rdquo; in plaats van &ldquo;GNU Linux&rdquo;?</a> 
58  
<a href="#usegnulinuxandandroid">Is it correct to say &ldquo;using Linux&rdquo; if it refers to using GNU/Linux and using Android?</a> 
 
136 | [-Isn't writing-]{+An operating system requires a kernel. Since+} the
| [-kernel most of-] {+GNU Project didn't develop a kernel, how can+} the
| [-work in an operating system? <span-] {+system be GNU?<span+}
| class="anchor-reference-id">(<a
| [-href="#kernelmost">#kernelmost</a>)</span>-]
| {+href="#nokernel">#nokernel</a>)</span>+} 
An operating system requires a kernel. Since the GNU Project didn't develop a kernel, how can the system be GNU?<span class="anchor-reference-id">(<a href="#nokernel">#nokernel</a>)</span> 
Is het schrijven van de kernel niet het meeste werk aan een besturingssysteem? <span class="anchor-reference-id">(<a href="#kernelmost">#kernelmost</a>)</span> 
161 | [-How about calling-]{+Stallman doesn't ask us to call him &ldquo;Richard
| Matthew Stallman&rdquo; every+} the [-system &ldquo;GliNUx&rdquo; (instead
| of &ldquo;GNU/Linux&rdquo;)?-] {+time. So why ask us to say
| &ldquo;GNU/Linux&rdquo; every time?+} <span
| class="anchor-reference-id">(<a [-href="#long1">#long1</a>)</span>-]
| {+href="#long4">#long4</a>)</span>+} 
Stallman doesn't ask us to call him &ldquo;Richard Matthew Stallman&rdquo; every the time. So why ask us to say &ldquo;GNU/Linux&rdquo; every time? <span class="anchor-reference-id">(<a href="#long4">#long4</a>)</span> 
Waarom noem je het systeem niet &ldquo;GliNUx&rdquo; (in plaats van &ldquo;GNU/Linux&rdquo;)? <span class="anchor-reference-id">(<a href="#long1">#long1</a>)</span> 
177 | [-Many companies contributed to-]{+systemd plays an important role in+}
| the {+GNU/Linux+} system as it is today; [-doesn't that mean-] {+are+} we
| [-ought-] {+obligated+} to call it [-GNU/Red&nbsp;Hat/Novell/Linux?-]
| {+GNU/systemd/Linux?+} <span class="anchor-reference-id">(<a
| [-href="#manycompanies">#manycompanies</a>)</span>-]
| {+href="#others">#others</a>)</span>+} 
systemd plays an important role in the GNU/Linux system as it is today; are we obligated to call it GNU/systemd/Linux? <span class="anchor-reference-id">(<a href="#others">#others</a>)</span> 
Veel bedrijven hebben bijgedragen aan het systeem zoals het nu is; betekent dat niet dat we het GNU/Redhat/Novell/Linux moeten noemen? <span class="anchor-reference-id">(<a href="#manycompanies">#manycompanies</a>)</span> 
191 | We're not talking about a distinct GNU version of Linux, the kernel. The
| free GNU/Linux distros do have a <a
| [-href="http://directory.fsf.org/project/linux">separate-]
| {+href="https://directory.fsf.org/wiki/Linux-libre">separate+} version
| of Linux</a>, since the &ldquo;standard&rdquo; version contains
| non[---]free firmware [-&ldquo;blobs&rdquo;.-] {+&ldquo;blobs.&rdquo;+} If
| this were part of the GNU Project, it could be considered &ldquo;GNU
| Linux&rdquo;; but we would not want to call it that, because it would be
| too confusing. 
We're not talking about a distinct GNU version of Linux, the kernel. The free GNU/Linux distros do have a <a href="https://directory.fsf.org/wiki/Linux-libre">separate version of Linux</a>, since the &ldquo;standard&rdquo; version contains nonfree firmware &ldquo;blobs.&rdquo; If this were part of the GNU Project, it could be considered &ldquo;GNU Linux&rdquo;; but we would not want to call it that, because it would be too confusing. 
We hebben het niet over een bepaalde GNU-versie van Linux, de kernel. De vrije GNU/Linux distributies hebben wel een <a href="http://directory.fsf.org/project/linux">aparte versie van Linux</a>, omdat de &ldquo;standaard&rdquo; versie niet-vrije firmware &ldquo;blobs&rdquo; bevat. Wanneer dit onderdeel zou zijn van het GNU-project zouden we het &ldquo;GNU Linux&rdquo;; kunnen noemen maar dat wordt te verwarrend. 
194 | [-Should we say &ldquo;GNU/BSD&rdquo; too?-]{+How is the name
| &ldquo;GNU/Linux&rdquo; pronounced?+} <span
| class="anchor-reference-id">(<a [-href="#bsd">#bsd</a>)</span>-]
| {+href="#pronounce">#pronounce</a>)</span>+} 
How is the name &ldquo;GNU/Linux&rdquo; pronounced? <span class="anchor-reference-id">(<a href="#pronounce">#pronounce</a>)</span> 
Zouden we ook &ldquo;GNU/BSD&rdquo; moeten gebruiken? <span class="anchor-reference-id">(<a href="#bsd">#bsd</a>)</span> 
195  
Please pronounce it as &ldquo;GNU slash Linux.&rdquo; If you don't pronounce the slash, people will think you are saying &ldquo;GNU Linux,&rdquo; which is <a href="#whyslash">not a suitable name for the combination</a>. 
 
196 | Why do you write [-&ldquo;GNU/Linux&rdquo; instead of-] &ldquo;GNU
| [-Linux&rdquo;?-] {+Emacs&rdquo; rather than &ldquo;GNU/Emacs&rdquo;?+}
| <span class="anchor-reference-id">(<a
| [-href="#whyslash">#whyslash</a>)</span>-]
| {+href="#whynoslash">#whynoslash</a>)</span>+} 
Why do you write &ldquo;GNU Emacs&rdquo; rather than &ldquo;GNU/Emacs&rdquo;? <span class="anchor-reference-id">(<a href="#whynoslash">#whynoslash</a>)</span> 
Waarom spel je het &ldquo;GNU/Linux&rdquo; in plaats van &ldquo;GNU Linux&rdquo;? <span class="anchor-reference-id">(<a href="#whyslash">#whyslash</a>)</span> 
210  
Wouldn't it be more effective to ask companies such as Mandrake, Red Hat and IBM to call their distributions &ldquo;GNU/Linux&rdquo; rather than asking individuals? <span class="anchor-reference-id">(<a href="#companies">#companies</a>)</span> 
Zou het niet handiger zijn om bedrijven als Mandrake, Red Hat en IBM te vragen hun distributies &ldquo;GNU/Linux&rdquo; te noemen in plaats van individuen? 
243 | The first such recursive acronym was TINT, &ldquo;TINT Is Not
| [-TECO&rdquo;.-] {+TECO.&rdquo;+} The author of TINT wrote another
| implementation of TECO (there were already many of them, for various
| systems), but instead of calling it by a dull name like
| &ldquo;<em>somethingorother</em> [-TECO&rdquo;,-] {+TECO,&rdquo;+} he
| thought of a clever amusing name. (That's what hacking means: <a
| href="http{+s+}://stallman.org/articles/on-hacking.html">playful
| cleverness</a>.) 
The first such recursive acronym was TINT, &ldquo;TINT Is Not TECO.&rdquo; The author of TINT wrote another implementation of TECO (there were already many of them, for various systems), but instead of calling it by a dull name like &ldquo;<em>somethingorother</em> TECO,&rdquo; he thought of a clever amusing name. (That's what hacking means: <a href="https://stallman.org/articles/on-hacking.html">playful cleverness</a>.) 
Zo'n eerste recursieve verwijzing was TINT, &ldquo;TINT Is Niet TECO&rdquo;. De schrijver van TINT schreef een nieuwe implementatie van TECO (er waren er al velen, voor diverse systemen), maar in plaats van het bedenken van een saaie naam als &ldquo;WatDanOok TECO&rdquo;, verzon hij een slimme en amusante naam. (Dat is ook wat het woord hacker betekent: <a href="http://stallman.org/articles/on-hacking.html">speelse slimmigheid</a>.) 
266  
Is it correct to say &ldquo;using Linux&rdquo; if it refers to using GNU/Linux and using Android? <span class="anchor-reference-id">(<a href="#usegnulinuxandandroidlinuxsyswithoutgnu">#usegnulinuxandandroidlinuxsyswithoutgnu</a>)</span> 
 
278 | He recognized this at the beginning. The {+<a
| href="https://ftp.funet.fi/pub/linux/historical/kernel/old-versions/RELNOTES-0.01">+}
| earliest Linux release [-notes said, <a
| href="http://ftp.funet.fi/pub/linux/historical/kernel/old-versions/RELNOTES-0.01">
| &ldquo;Most of the tools used with linux are GNU software and are under
| the GNU copyleft. These tools aren't in the distribution - ask me (or GNU)
| for more info&rdquo;</a>.-] {+notes</a> said:+} 
He recognized this at the beginning. The <a href="https://ftp.funet.fi/pub/linux/historical/kernel/old-versions/RELNOTES-0.01"> earliest Linux release notes</a> said: 
Hij kwam hier in het begin al mee. In de eerste Linux release notes stond al, <a href="http://ftp.funet.fi/pub/linux/historical/kernel/old-versions/RELNOTES-0.01"> &ldquo;De meeste hulpmiddelen die linux gebruikt zijn GNU programma's en vallen onder de GNU auteursplicht. Die programma's zitten niet in deze distributie - vraag mij (of GNU) voor meer informatie&rdquo;</a>. 
279 | [-He recognized this at the beginning. The earliest Linux release notes
| said, <a
| href="http://ftp.funet.fi/pub/linux/historical/kernel/old-versions/RELNOTES-0.01">
| &ldquo;Most-]{+Most+} of the tools used with linux are GNU software and
| are under the GNU copyleft. These tools aren't in the distribution - ask
| me (or GNU) for more [-info&rdquo;</a>.-] {+info.+} 
Most of the tools used with linux are GNU software and are under the GNU copyleft. These tools aren't in the distribution - ask me (or GNU) for more info. 
Hij kwam hier in het begin al mee. In de eerste Linux release notes stond al, <a href="http://ftp.funet.fi/pub/linux/historical/kernel/old-versions/RELNOTES-0.01"> &ldquo;De meeste hulpmiddelen die linux gebruikt zijn GNU programma's en vallen onder de GNU auteursplicht. Die programma's zitten niet in deze distributie - vraag mij (of GNU) voor meer informatie&rdquo;</a>. 
282 Nieuw
| Making the GNU Hurd work well enough to compete with Linux would be a big
| job, and it's not clearly necessary. The only thing ethically wrong with
| Linux as a kernel is its inclusion of firmware &ldquo;blobs&rdquo;; the
| best fix for that problem is <a
| [-href="http://fsf.org/campaigns/priority-projects">-]
| {+href="https://www.fsf.org/campaigns/priority-projects">+} developing
| free replacement for the blobs</a>. 
Making the GNU Hurd work well enough to compete with Linux would be a big job, and it's not clearly necessary. The only thing ethically wrong with Linux as a kernel is its inclusion of firmware &ldquo;blobs&rdquo;; the best fix for that problem is <a href="https://www.fsf.org/campaigns/priority-projects"> developing free replacement for the blobs</a>. 
Om GNU Hurd net zo goed te maken als Linux zou een zware taak zijn en is niet echt nodig. Het enige ethisch verkeerde aan de kernel Linux is dat het firmware&ldquo;blobs&rdquo; bevat; de beste oplossing hiervoor is het <a href="http://fsf.org/campaigns/priority-projects"> ontwikkelen van vrije vervangingen voor deze blobs</a>. 
324 || No change detected. The change might only be in amounts of spaces. 
Please see the <a href="/server/standards/README.translations.html">Translations README</a> for information on coordinating and contributing translations of this article. 
We doen ons best om goede vertalingen te maken maar staan altijd open voor verbeteringen. Suggesties, op- en aanmerkingen sturen aan: <a href="mailto:web-translators@gnu.org">&lt;web-translators@gnu.org&gt;</a>.</p> <p>Zie <a href="/server/standards/README.translations.html"> Translations README</a> voor informatie over het onderhoud van vertalingen op deze website.