From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: it_IT: address invalid reference warnings
Date: Sun, 07 Jun 2020 00:06:02 +0200 [thread overview]
Message-ID: <11587824.O9o76ZdvQC@harkonnen> (raw)
In-Reply-To: <3060760.44csPzL39Z@harkonnen>
I re-read the documents with the full context.
Moving to the directive :doc: for only those two references (like I was
arguing in the previous email) will make the document inconsistent.
So, the patch is fine for me as it is.
I will finish and push the translation for ../core-api/symbol-namespace.rst
and move the link again
On Tuesday, June 2, 2020 10:37:21 AM CEST Federico Vaga wrote:
> On Sunday, May 31, 2020 8:56:18 PM CEST Lukas Bulwahn wrote:
> > Documentation generation warns:
> > it_IT/kernel-hacking/hacking.rst:
> > WARNING: unknown document: ../core-api/symbol/namespaces
> >
> > it_IT/process/5.Posting.rst:
> > WARNING: undefined label: it_email_clients
> >
> > it_IT/process/submitting-patches.rst:
> > WARNING: undefined label: it_email_clients
> >
> > it_IT/process/howto.rst:
> > WARNING: undefined label: it_managementstyle
> >
> > Refer to English documentation, as Italian translation does not exist,
> > and
>
> The file exists! On my disk :D
> My mistake, I have an almost done translation for that and of course I do
> not see the warning.
>
> > add labels for Italian process documents to resolve label references.
>
> I think we have agreed to not use labels but instead to sue the directive
>
> :doc: instead. This fix should happen in the document that points here. When
> :I
> posted the new translations I removed those labels but forgot to fix:
> it_IT/process/5.Posting.rst, it_IT/process/submitting-patches.rst and it_IT/
> process/howto.rst
>
> :doc:`../process/email-clients`
> :doc:`../process/management-style`
>
> I should be more meticulous and regenerate the full translation every time.
> Lesson learned. Sorry for that and thanks
>
> > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> > ---
> > Jonathan, please pick this quick fix of warnings.
> >
> > applies on doc-next and next-20200529
> >
> > Documentation/translations/it_IT/kernel-hacking/hacking.rst | 4 ++--
> > Documentation/translations/it_IT/process/email-clients.rst | 2 ++
> > Documentation/translations/it_IT/process/management-style.rst | 2 ++
> > 3 files changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/translations/it_IT/kernel-hacking/hacking.rst
> > b/Documentation/translations/it_IT/kernel-hacking/hacking.rst index
> > 6aab27a8d323..e9a2e92134f0 100644
> > --- a/Documentation/translations/it_IT/kernel-hacking/hacking.rst
> > +++ b/Documentation/translations/it_IT/kernel-hacking/hacking.rst
> > @@ -634,7 +634,7 @@ Definita in ``include/linux/export.h``
> >
> > Questa è una variate di `EXPORT_SYMBOL()` che permette di specificare uno
> > spazio dei nomi. Lo spazio dei nomi è documentato in
> >
> > -:doc:`../core-api/symbol-namespaces`
> > +:doc:`../../../core-api/symbol-namespaces`
> >
> > :c:func:`EXPORT_SYMBOL_NS_GPL()`
> >
> > --------------------------------
> >
> > @@ -643,7 +643,7 @@ Definita in ``include/linux/export.h``
> >
> > Questa è una variate di `EXPORT_SYMBOL_GPL()` che permette di specificare
> >
> > uno spazio dei nomi. Lo spazio dei nomi è documentato in
> > -:doc:`../core-api/symbol-namespaces`
> > +:doc:`../../../core-api/symbol-namespaces`
> >
> > Procedure e convenzioni
> > =======================
> >
> > diff --git a/Documentation/translations/it_IT/process/email-clients.rst
> > b/Documentation/translations/it_IT/process/email-clients.rst index
> > 89abf6d325f2..66d3d65776f7 100644
> > --- a/Documentation/translations/it_IT/process/email-clients.rst
> > +++ b/Documentation/translations/it_IT/process/email-clients.rst
> > @@ -3,6 +3,8 @@
> >
> > :Original: :doc:`../../../process/email-clients`
> > :Translator: Alessia Mantegazza <amantegazza@vaga.pv.it>
> >
> > +.. _it_email_clients:
> > +
> >
> > Informazioni sui programmi di posta elettronica per Linux
> > =========================================================
> >
> > diff --git a/Documentation/translations/it_IT/process/management-style.rst
> > b/Documentation/translations/it_IT/process/management-style.rst index
> > c709285138a7..76ed074082ea 100644
> > --- a/Documentation/translations/it_IT/process/management-style.rst
> > +++ b/Documentation/translations/it_IT/process/management-style.rst
> > @@ -3,6 +3,8 @@
> >
> > :Original: :doc:`../../../process/management-style`
> > :Translator: Alessia Mantegazza <amantegazza@vaga.pv.it>
> >
> > +.. _it_managementstyle:
> > +
> >
> > Il modello di gestione del kernel Linux
> > =======================================
next prev parent reply other threads:[~2020-06-06 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 18:56 [PATCH] docs: it_IT: address invalid reference warnings Lukas Bulwahn
2020-06-02 8:37 ` Federico Vaga
2020-06-06 22:06 ` Federico Vaga [this message]
2020-06-08 15:25 ` Jonathan Corbet
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=11587824.O9o76ZdvQC@harkonnen \
--to=federico.vaga@vaga.pv.it \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@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