On 2019-11-13 10:37, Markus Heiser wrote:
my 2cent ..
I have a doubt that translating has to be a part of the kernel
development.
I have a conflict of interests of course, and because of it I disagree.
Minimal English is one of the prerequisites to be a part of the
community.
In a community there are active members and passive ones. It is true
that
active members need to know English (it is written in the
documentation).
But passive members are following the development, they are learning
from it,
they profit from its openness. For these users English could be a
problem, or
an imposition; nowadays students future is shaped based on the language
they
study at school (studying German/French/Italian/Spanish does not open
the
same doors).
I believe that the Linux kernel and many other open source projects
should
not just help the industry to cut their costs, but they should also play
a
social role: education, sharing knowledge. Documentation in general, and
translations as well, are part of this second world.
Maintainers do not master foreign languages
they are forced to commit blindly without quality assurance.
In some cases maintainers have been forced to accept code blindly
without
quality assurance because they do not own the hardware for which they
are
accepting patches.
APIs will never be translated and
the translation of articles is at random.
IMO a spin-off might focus on translations.
I may agree on this, only if there is an official place where to put
them,
like:
https://www.kernel.org/doc/html/zh_CN/latest/
Otherwise, a translation on a random git<whatever> service is useless
because it does
not have visibility/authority.
-- Markus --
Am 12.11.19 um 16:59 schrieb Jani Nikula:
On Tue, 12 Nov 2019, Jonathan Corbet <corbet@xxxxxxx> wrote:
On Tue, 12 Nov 2019 16:17:32 +0200
Jani Nikula <jani.nikula@xxxxxxxxxxxxxxx> wrote:
Fix the references in both places to actually make them cross
references. See below.
BR,
Jani.
diff --git a/Documentation/process/programming-language.rst
b/Documentation/process/programming-language.rst
index e5f5f065dc24..59efa6d7a053 100644
--- a/Documentation/process/programming-language.rst
+++ b/Documentation/process/programming-language.rst
@@ -3,7 +3,7 @@
Programming Language
====================
-The kernel is written in the C programming language
[c-language]_.
+The kernel is written in the C programming language
`[c-language]`_.
More precisely, the kernel is typically compiled with ``gcc``
[gcc]_
under ``-std=gnu89`` [gcc-c-dialect-options]_: the GNU dialect of
ISO C90
(including some C99 features).
@@ -34,7 +34,7 @@ in order to feature detect which ones can be used
and/or to shorten the code.
Please refer to ``include/linux/compiler_attributes.h`` for more
information.
-.. [c-language]
http://www.open-std.org/jtc1/sc22/wg14/www/standards
+.. _[c-language]:
http://www.open-std.org/jtc1/sc22/wg14/www/standards
.. [gcc] https://gcc.gnu.org
.. [clang] https://clang.llvm.org
.. [icc] https://software.intel.com/en-us/c-compilers
That fixes this particular instance, while leaving the adjacent ones
untouched :)
Yeah, that was just a quick hack to prove the point. Perhaps Miguel
can
provide the proper patch? ;)
I think this is a good change, especially if applied to all
instances. I
also wonder, though, if we should adopt a rule that translations need
unique labels - prepend "IT-" or some such for the Italian
translation,
for example?
I *think* the references like above (when done properly) are local to
the file. It's the labels that perhaps need this.
Sphinx also has some i18n support which I believe we aren't using, and
it would stand to reason this is covered there. But that probably
needs
some dedication from Someone(tm) to figure out.
BR,
Jani.
--
Federico Vaga
http://www.federicovaga.it/
