All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/4] Documentation: clean up subproject index boilerplate
Date: Thu, 13 Nov 2025 18:59:46 +0200	[thread overview]
Message-ID: <db45a19716d39b6dd89e3fbc85067673fdb0d335@intel.com> (raw)
In-Reply-To: <87o6p5sxhs.fsf@trenco.lwn.net>

On Thu, 13 Nov 2025, Jonathan Corbet <corbet@lwn.net> wrote:
> Jani Nikula <jani.nikula@intel.com> writes:
>
>> Only very lightly tested.
>>
>> Jani Nikula (4):
>>   Documentation: remove subproject index links deep in the structure
>>   Documentation: streamline subproject index link in translations
>>   Documentation: include the boilerplate for SPHINXDIRS index link
>>   Documentation: use a source-read extension to include the index
>>     boilerplate
>
> That bit of repeated gunk has been on my list to look at for a while,
> thanks for digging into it.  Looking forward to the second version.

As I said elsewhere, I didn't realize you could use SPHINXDIRS deeper
than the top level. The implementation is slightly problematic for
translations/. I don't suppose you want to have English "Indices"
heading when using, say, SPHINXDIRS=translations/it_IT/doc-guide?

I guess the alternatives are:

1) Keep having the index links manually in translations/, and don't add
   the template for files there.

2) Accept English "Indices" as a tradeoff.

3) Come up with a system of having multiple language templates for the
   indices, and use them automatically under translations/.

We could also do 2) first and expand to 3) later.

BR,
Jani.



-- 
Jani Nikula, Intel

  reply	other threads:[~2025-11-13 17:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12 11:56 [PATCH 0/4] Documentation: clean up subproject index boilerplate Jani Nikula
2025-11-12 11:56 ` [PATCH 1/4] Documentation: remove subproject index links deep in the structure Jani Nikula
2025-11-12 13:27   ` Mauro Carvalho Chehab
2025-11-12 11:56 ` [PATCH 2/4] Documentation: streamline subproject index link in translations Jani Nikula
2025-11-12 11:56 ` [PATCH 3/4] Documentation: include the boilerplate for SPHINXDIRS index link Jani Nikula
2025-11-12 13:35   ` Mauro Carvalho Chehab
2025-11-13  8:04     ` Jani Nikula
2025-11-13 10:11       ` Mauro Carvalho Chehab
2025-11-12 11:56 ` [PATCH 4/4] Documentation: use a source-read extension to include the index boilerplate Jani Nikula
2025-11-12 13:39   ` Mauro Carvalho Chehab
2025-11-13  8:12     ` Jani Nikula
2025-11-13 10:25       ` Mauro Carvalho Chehab
2025-11-13 19:36       ` Randy Dunlap
2025-11-13  6:50 ` [PATCH 0/4] Documentation: clean up subproject " Randy Dunlap
2025-11-13 16:33 ` Jonathan Corbet
2025-11-13 16:59   ` Jani Nikula [this message]
2025-12-04 13:43     ` 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=db45a19716d39b6dd89e3fbc85067673fdb0d335@intel.com \
    --to=jani.nikula@intel.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.