From: Jani Nikula <jani.nikula@linux.intel.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Federico Vaga <federico.vaga@vaga.pv.it>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Subject: Re: On global citations, URLs and translations
Date: Tue, 12 Nov 2019 16:17:32 +0200 [thread overview]
Message-ID: <87a79141s3.fsf@intel.com> (raw)
In-Reply-To: <CANiq72=mBLHTLtstBPU4TZT2DOAnYrtbd4SDh0tjkjo07ns=4w@mail.gmail.com>
On Tue, 12 Nov 2019, Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrote:
> Hi Jonathan, Federico,
>
> While I was writing some new docs for something else, I found that
> given that citations are global, some translations are overriding the
> normal citations.
>
> For instance, on:
>
> https://www.kernel.org/doc/html/latest/process/programming-language.html
>
> We have the first link pointing to:
>
> https://www.kernel.org/doc/html/latest/translations/it_IT/process/programming-language.html#c-language
>
> i.e. the Italian translation; which is clearly not intended. Rather,
> it should point to the URL the citation points to.
>
> This may have been my mistake originally, since I wrote the original
> file and used citations. Checking now other files around in Docs/, I
> see almost nobody uses citations and simply put raw URLs, have a
> bottom section on References/Bibliography or use inline hyperlinks.
>
> To be honest, after seeing how citations look in the rendered output,
> and given they are global, I think it may be simpler to just use
> inline hyperlinks. On the other hand, it is nice to have a common set
> of citations (to keep up to date both translations and other
> documents). However, if we do this, I guess we need to encourage
> people to deal with the Sphinx WARNINGs.
>
> How should we handle this? What should be encouraged for new docs?
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
diff --git a/Documentation/translations/it_IT/process/programming-language.rst b/Documentation/translations/it_IT/process/programming-language.rst
index f4b006395849..b30661731911 100644
--- a/Documentation/translations/it_IT/process/programming-language.rst
+++ b/Documentation/translations/it_IT/process/programming-language.rst
@@ -8,7 +8,7 @@
Linguaggio di programmazione
============================
-Il kernel è scritto nel linguaggio di programmazione C [c-language]_.
+Il kernel è scritto nel linguaggio di programmazione C `[c-language]`_.
Più precisamente, il kernel viene compilato con ``gcc`` [gcc]_ usando
l'opzione ``-std=gnu89`` [gcc-c-dialect-options]_: il dialetto GNU
dello standard ISO C90 (con l'aggiunta di alcune funzionalità da C99)
@@ -41,7 +41,7 @@ possono usare e/o per accorciare il codice.
Per maggiori informazioni consultate il file d'intestazione
``include/linux/compiler_attributes.h``.
-.. [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
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2019-11-12 14:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 6:54 On global citations, URLs and translations Miguel Ojeda
2019-11-12 14:17 ` Jani Nikula [this message]
2019-11-12 15:42 ` Jonathan Corbet
2019-11-12 15:59 ` Jani Nikula
2019-11-13 9:37 ` Markus Heiser
2019-11-13 21:49 ` Federico Vaga
2019-11-14 13:22 ` Jonathan Corbet
2019-11-14 0:54 ` Miguel Ojeda
2019-11-14 8:35 ` Federico Vaga
2019-11-14 9:25 ` Jani Nikula
2019-11-13 21:07 ` Federico Vaga
2019-11-14 9:28 ` Jani Nikula
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a79141s3.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=linux-doc@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).