From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Federico Vaga <federico.vaga@vaga.pv.it>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Subject: Re: On global citations, URLs and translations
Date: Tue, 12 Nov 2019 17:59:21 +0200 [thread overview]
Message-ID: <871rud3x2e.fsf@intel.com> (raw)
In-Reply-To: <20191112084257.4cca2d4c@lwn.net>
On Tue, 12 Nov 2019, Jonathan Corbet <corbet@lwn.net> wrote:
> On Tue, 12 Nov 2019 16:17:32 +0200
> Jani Nikula <jani.nikula@linux.intel.com> 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.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2019-11-12 15:59 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
2019-11-12 15:42 ` Jonathan Corbet
2019-11-12 15:59 ` Jani Nikula [this message]
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=871rud3x2e.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).