[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/philosophy/po stallman-kth.fr.po stallman-k...
|
From: |
GNUN |
|
Subject: |
www/philosophy/po stallman-kth.fr.po stallman-k... |
|
Date: |
Tue, 14 Sep 2021 18:33:28 -0400 (EDT) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 21/09/14 18:33:28
Modified files:
philosophy/po : stallman-kth.fr.po stallman-kth.pot
stallman-kth.ru.po
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/stallman-kth.fr.po?cvsroot=www&r1=1.57&r2=1.58
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/stallman-kth.pot?cvsroot=www&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/stallman-kth.ru.po?cvsroot=www&r1=1.21&r2=1.22
Patches:
Index: stallman-kth.fr.po
===================================================================
RCS file: /web/www/www/philosophy/po/stallman-kth.fr.po,v
retrieving revision 1.57
retrieving revision 1.58
diff -u -b -r1.57 -r1.58
--- stallman-kth.fr.po 14 Sep 2021 21:12:30 -0000 1.57
+++ stallman-kth.fr.po 14 Sep 2021 22:33:27 -0000 1.58
@@ -9,7 +9,7 @@
msgid ""
msgstr ""
"Project-Id-Version: stallman-kth\n"
-"POT-Creation-Date: 2021-09-14 19:56+0000\n"
+"POT-Creation-Date: 2021-09-14 22:26+0000\n"
"PO-Revision-Date: 2021-09-14 23:11+0200\n"
"Last-Translator: Thérèse Godefroy <godef.th AT free.fr>\n"
"Language-Team: French <trad-gnu@april.org>\n"
@@ -17,6 +17,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2021-09-14 22:26+0000\n"
"Plural-Forms: \n"
"X-Generator: Gtranslator 2.91.5\n"
@@ -1092,18 +1093,52 @@
"c'était du « Pascal mal fichu »."
#. type: Content of: <div><p>
+# | Pastel was a very complicated language including features such as
+# | parametrized types and explicit type parameters and many complicated
+# | things. The compiler was of course written in this language, and had many
+# | complicated features to optimize the use of these things. For example:
+# | the type “string” in that language was a parameterized type;
+# | you could say [-“string(n)”-] {+<code>string(n)</code>+} if
+# | you wanted a string of a particular length; you could also just say
+# | [-“string,”-] {+<code>string</code>,+} and the parameter would
+# | be determined from the context. Now, strings are very important, and it
+# | is necessary for a lot of constructs that use them to run fast, and this
+# | means that they had to have a lot of features to detect such things as:
+# | when the declared length of a string is an argument that is known to be
+# | constant throughout the function, to save to save the value and optimize
+# | the code they're going to produce, many complicated things. But I did get
+# | to see in this compiler how to do automatic register allocation, and some
+# | ideas about how to handle different sorts of machines.
+#, fuzzy
+#| msgid ""
+#| "Pastel was a very complicated language including features such as "
+#| "parametrized types and explicit type parameters and many complicated "
+#| "things. The compiler was of course written in this language, and had "
+#| "many complicated features to optimize the use of these things. For "
+#| "example: the type “string” in that language was a "
+#| "parameterized type; you could say “string(n)” if you wanted a "
+#| "string of a particular length; you could also just say “string,"
+#| "” and the parameter would be determined from the context. Now, "
+#| "strings are very important, and it is necessary for a lot of constructs "
+#| "that use them to run fast, and this means that they had to have a lot of "
+#| "features to detect such things as: when the declared length of a string "
+#| "is an argument that is known to be constant throughout the function, to "
+#| "save to save the value and optimize the code they're going to produce, "
+#| "many complicated things. But I did get to see in this compiler how to do "
+#| "automatic register allocation, and some ideas about how to handle "
+#| "different sorts of machines."
msgid ""
"Pastel was a very complicated language including features such as "
"parametrized types and explicit type parameters and many complicated "
"things. The compiler was of course written in this language, and had many "
"complicated features to optimize the use of these things. For example: the "
"type “string” in that language was a parameterized type; you "
-"could say “string(n)” if you wanted a string of a particular "
-"length; you could also just say “string,” and the parameter "
-"would be determined from the context. Now, strings are very important, and "
-"it is necessary for a lot of constructs that use them to run fast, and this "
-"means that they had to have a lot of features to detect such things as: when "
-"the declared length of a string is an argument that is known to be constant "
+"could say <code>string(n)</code> if you wanted a string of a particular "
+"length; you could also just say <code>string</code>, and the parameter would "
+"be determined from the context. Now, strings are very important, and it is "
+"necessary for a lot of constructs that use them to run fast, and this means "
+"that they had to have a lot of features to detect such things as: when the "
+"declared length of a string is an argument that is known to be constant "
"throughout the function, to save to save the value and optimize the code "
"they're going to produce, many complicated things. But I did get to see in "
"this compiler how to do automatic register allocation, and some ideas about "
@@ -1128,13 +1163,59 @@
"glaner quelques idées sur la façon de gérer différents types de machines."
#. type: Content of: <div><p>
+# | Well, since this compiler already compiled PASTEL, what I needed to do was
+# | add a front-end for C, which I did, and add a back-end for the 68000 which
+# | I expected to be my first target machine. But I ran into a serious
+# | problem. Because the PASTEL language was defined not to require you to
+# | declare something before you used it, the declarations and uses could be
+# | in any order, in other words: Pascal's [-“forward”-]
+# | {+<code>forward</code>+} declaration was obsolete, because of this it was
+# | necessary to read in an entire program, and keep it in core, and then
+# | process it all at once. The result was that the intermediate storage used
+# | in the compiler, the size of the memory needed, was proportional to the
+# | size of your file. And this also included stack-space, you needed
+# | gigantic amounts of stack space, and what I found as a result was: that
+# | the 68000 system available to me could not run the compiler. Because it
+# | was a horrible version of Unix that gave you a limit of something like 16K
+# | words of stack, this despite the existence of six megabytes in the
+# | machine, you could only have 16Kw of stack or something like that. And of
+# | course to generate its conflict matrix to see which temporary values
+# | conflicted, or was alive at the same time as which others, it needed a
+# | quadratic matrix of bits, and that for large functions that would get it
+# | to hundreds of thousands of bytes. So I managed to debug the first pass
+# | of the ten or so passes of the compiler, cross compiled on to that
+# | machine, and then found that the second one could never run.
+#, fuzzy
+#| msgid ""
+#| "Well, since this compiler already compiled PASTEL, what I needed to do "
+#| "was add a front-end for C, which I did, and add a back-end for the 68000 "
+#| "which I expected to be my first target machine. But I ran into a serious "
+#| "problem. Because the PASTEL language was defined not to require you to "
+#| "declare something before you used it, the declarations and uses could be "
+#| "in any order, in other words: Pascal's “forward” declaration "
+#| "was obsolete, because of this it was necessary to read in an entire "
+#| "program, and keep it in core, and then process it all at once. The "
+#| "result was that the intermediate storage used in the compiler, the size "
+#| "of the memory needed, was proportional to the size of your file. And "
+#| "this also included stack-space, you needed gigantic amounts of stack "
+#| "space, and what I found as a result was: that the 68000 system available "
+#| "to me could not run the compiler. Because it was a horrible version of "
+#| "Unix that gave you a limit of something like 16K words of stack, this "
+#| "despite the existence of six megabytes in the machine, you could only "
+#| "have 16Kw of stack or something like that. And of course to generate its "
+#| "conflict matrix to see which temporary values conflicted, or was alive at "
+#| "the same time as which others, it needed a quadratic matrix of bits, and "
+#| "that for large functions that would get it to hundreds of thousands of "
+#| "bytes. So I managed to debug the first pass of the ten or so passes of "
+#| "the compiler, cross compiled on to that machine, and then found that the "
+#| "second one could never run."
msgid ""
"Well, since this compiler already compiled PASTEL, what I needed to do was "
"add a front-end for C, which I did, and add a back-end for the 68000 which I "
"expected to be my first target machine. But I ran into a serious problem. "
"Because the PASTEL language was defined not to require you to declare "
"something before you used it, the declarations and uses could be in any "
-"order, in other words: Pascal's “forward” declaration was "
+"order, in other words: Pascal's <code>forward</code> declaration was "
"obsolete, because of this it was necessary to read in an entire program, and "
"keep it in core, and then process it all at once. The result was that the "
"intermediate storage used in the compiler, the size of the memory needed, "
Index: stallman-kth.pot
===================================================================
RCS file: /web/www/www/philosophy/po/stallman-kth.pot,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- stallman-kth.pot 14 Sep 2021 20:03:34 -0000 1.18
+++ stallman-kth.pot 14 Sep 2021 22:33:27 -0000 1.19
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: stallman-kth.html\n"
-"POT-Creation-Date: 2021-09-14 19:56+0000\n"
+"POT-Creation-Date: 2021-09-14 22:26+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -619,12 +619,12 @@
"things. The compiler was of course written in this language, and had many "
"complicated features to optimize the use of these things. For example: the "
"type “string” in that language was a parameterized type; you "
-"could say “string(n)” if you wanted a string of a particular "
-"length; you could also just say “string,” and the parameter "
-"would be determined from the context. Now, strings are very important, and "
-"it is necessary for a lot of constructs that use them to run fast, and this "
-"means that they had to have a lot of features to detect such things as: when "
-"the declared length of a string is an argument that is known to be constant "
+"could say <code>string(n)</code> if you wanted a string of a particular "
+"length; you could also just say <code>string</code>, and the parameter would "
+"be determined from the context. Now, strings are very important, and it is "
+"necessary for a lot of constructs that use them to run fast, and this means "
+"that they had to have a lot of features to detect such things as: when the "
+"declared length of a string is an argument that is known to be constant "
"throughout the function, to save to save the value and optimize the code "
"they're going to produce, many complicated things. But I did get to see in "
"this compiler how to do automatic register allocation, and some ideas about "
@@ -638,7 +638,7 @@
"expected to be my first target machine. But I ran into a serious problem. "
"Because the PASTEL language was defined not to require you to declare "
"something before you used it, the declarations and uses could be in any "
-"order, in other words: Pascal's “forward” declaration was "
+"order, in other words: Pascal's <code>forward</code> declaration was "
"obsolete, because of this it was necessary to read in an entire program, and "
"keep it in core, and then process it all at once. The result was that the "
"intermediate storage used in the compiler, the size of the memory needed, "
Index: stallman-kth.ru.po
===================================================================
RCS file: /web/www/www/philosophy/po/stallman-kth.ru.po,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- stallman-kth.ru.po 14 Sep 2021 20:03:34 -0000 1.21
+++ stallman-kth.ru.po 14 Sep 2021 22:33:27 -0000 1.22
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: stallman-kth.html\n"
-"POT-Creation-Date: 2021-09-14 19:56+0000\n"
+"POT-Creation-Date: 2021-09-14 22:26+0000\n"
"PO-Revision-Date: 2020-07-01 17:17+0000\n"
"Last-Translator: Ineiev <ineiev@gnu.org>\n"
"Language-Team: Russian <www-ru-list@gnu.org>\n"
@@ -1508,17 +1508,17 @@
# | things. The compiler was of course written in this language, and had many
# | complicated features to optimize the use of these things. For example:
# | the type “string” in that language was a parameterized type;
-# | you could say “string(n)” if you wanted a string of a
-# | particular length; you could also just say [-“string”,-]
-# | {+“string,”+} and the parameter would be determined from the
-# | context. Now, strings are very important, and it is necessary for a lot
-# | of constructs that use them to run fast, and this means that they had to
-# | have a lot of features to detect such things as: when the declared length
-# | of a string is an argument that is known to be constant throughout the
-# | function, to save to save the value and optimize the code they're going to
-# | produce, many complicated things. But I did get to see in this compiler
-# | how to do automatic register allocation, and some ideas about how to
-# | handle different sorts of machines.
+# | you could say [-“string(n)”-] {+<code>string(n)</code>+} if
+# | you wanted a string of a particular length; you could also just say
+# | [-“string”,-] {+<code>string</code>,+} and the parameter would
+# | be determined from the context. Now, strings are very important, and it
+# | is necessary for a lot of constructs that use them to run fast, and this
+# | means that they had to have a lot of features to detect such things as:
+# | when the declared length of a string is an argument that is known to be
+# | constant throughout the function, to save to save the value and optimize
+# | the code they're going to produce, many complicated things. But I did get
+# | to see in this compiler how to do automatic register allocation, and some
+# | ideas about how to handle different sorts of machines.
#, fuzzy
#| msgid ""
#| "Pastel was a very complicated language including features such as "
@@ -1543,12 +1543,12 @@
"things. The compiler was of course written in this language, and had many "
"complicated features to optimize the use of these things. For example: the "
"type “string” in that language was a parameterized type; you "
-"could say “string(n)” if you wanted a string of a particular "
-"length; you could also just say “string,” and the parameter "
-"would be determined from the context. Now, strings are very important, and "
-"it is necessary for a lot of constructs that use them to run fast, and this "
-"means that they had to have a lot of features to detect such things as: when "
-"the declared length of a string is an argument that is known to be constant "
+"could say <code>string(n)</code> if you wanted a string of a particular "
+"length; you could also just say <code>string</code>, and the parameter would "
+"be determined from the context. Now, strings are very important, and it is "
+"necessary for a lot of constructs that use them to run fast, and this means "
+"that they had to have a lot of features to detect such things as: when the "
+"declared length of a string is an argument that is known to be constant "
"throughout the function, to save to save the value and optimize the code "
"they're going to produce, many complicated things. But I did get to see in "
"this compiler how to do automatic register allocation, and some ideas about "
@@ -1577,23 +1577,23 @@
# | 68000 which I expected to be my first target machine. But I ran into a
# | serious problem. Because the PASTEL language was defined not to require
# | you to declare something before you used it, the declarations and uses
-# | could be in any order, in other words: Pascal's “forward”
-# | declaration was obsolete, because of this it was necessary to read in an
-# | entire program, and keep it in core, and then process it all at once. The
-# | result was that the intermediate storage used in the compiler, the size of
-# | the memory needed, was proportional to the size of your file. And this
-# | also included stack-space, you needed gigantic amounts of stack space, and
-# | what I found as a result was: that the 68000 system available to me could
-# | not run the compiler. Because it was a horrible version of Unix that gave
-# | you a limit of something like 16K words of stack, this despite the
-# | existence of six megabytes in the machine, you could only have 16Kw of
-# | stack or something like that. And of course to generate its conflict
-# | matrix to see which temporary values conflicted, or was alive at the same
-# | time as which others, it needed a quadratic matrix of bits, and that for
-# | large functions that would get it to hundreds of thousands of bytes. So
-# | [-i-] {+I+} managed to debug the first pass of the ten or so passes of the
-# | compiler, cross compiled on to that machine, and then found that the
-# | second one could never run.
+# | could be in any order, in other words: Pascal's [-“forward”-]
+# | {+<code>forward</code>+} declaration was obsolete, because of this it was
+# | necessary to read in an entire program, and keep it in core, and then
+# | process it all at once. The result was that the intermediate storage used
+# | in the compiler, the size of the memory needed, was proportional to the
+# | size of your file. And this also included stack-space, you needed
+# | gigantic amounts of stack space, and what I found as a result was: that
+# | the 68000 system available to me could not run the compiler. Because it
+# | was a horrible version of Unix that gave you a limit of something like 16K
+# | words of stack, this despite the existence of six megabytes in the
+# | machine, you could only have 16Kw of stack or something like that. And of
+# | course to generate its conflict matrix to see which temporary values
+# | conflicted, or was alive at the same time as which others, it needed a
+# | quadratic matrix of bits, and that for large functions that would get it
+# | to hundreds of thousands of bytes. So [-i-] {+I+} managed to debug the
+# | first pass of the ten or so passes of the compiler, cross compiled on to
+# | that machine, and then found that the second one could never run.
#, fuzzy
#| msgid ""
#| "Well, since this compiler already compiled PASTEL, what i needed to do "
@@ -1624,7 +1624,7 @@
"expected to be my first target machine. But I ran into a serious problem. "
"Because the PASTEL language was defined not to require you to declare "
"something before you used it, the declarations and uses could be in any "
-"order, in other words: Pascal's “forward” declaration was "
+"order, in other words: Pascal's <code>forward</code> declaration was "
"obsolete, because of this it was necessary to read in an entire program, and "
"keep it in core, and then process it all at once. The result was that the "
"intermediate storage used in the compiler, the size of the memory needed, "