linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] docs: Only load the translations extension for HTML output
Date: Thu, 15 Feb 2024 20:10:44 +0900	[thread overview]
Message-ID: <d34e3dce-0a16-48fc-b3dd-e83ff3568baa@gmail.com> (raw)
In-Reply-To: <3c037ee8-210b-4bb9-9877-35637749d2b1@oracle.com>

Hi Vegard,

On 2024/02/15 15:22, Vegard Nossum wrote:
> 
> On 15/02/2024 03:43, Akira Yokosawa wrote:
>> On 2024/02/15 8:25, Jonathan Corbet wrote:
>>> +#
>>> +# Only enable the translation extension if we are building the HTML docs;
>>> +# it brings no value otherwise and can cause problems.
>>> +#
>>> +if 'html' in sys.argv:
>>> +    extensions.append('translations')
>>
>> I tested incremental build of latexdocs against Sphinx 7.2.6 as follows:
> 
> [...]
> 
>> WARNING: unknown node type: <LanguagesNode: <#text: 'Chinese (Simpl ...'><#text: 'Chinese (Tradi ... ...>
>>
>> Exception occurred:
>>    File "/home/akira/sphinx-7.2.6/lib/python3.10/site-packages/docutils/nodes.py", line 2068, in unknown_departure
>>      raise NotImplementedError(
>> NotImplementedError: <class 'sphinx.writers.latex.LaTeXTranslator'> departing unknown node type: LanguagesNode
>> The full traceback has been saved in /tmp/sphinx-err-3inve171.log, if you want to report the issue to the developers.
> 
> Jon, this is pretty much what I said would happen here:
> 
> https://lore.kernel.org/all/8b51b6d6-0360-4f42-9b96-02e0ccd0b34f@oracle.com/
> 
> I have a proper fix that should fix all errors everywhere:
> 
> https://lore.kernel.org/all/4806c264-1076-401b-bb5f-283fb7b68fb3@oracle.com/

Oh, that's even better!

> 
> Why not use that? I'll do a proper submission, I was just waiting a
> couple of days to see if anybody else would would test it too.

I didn't respond because I mistook your words

> I'll test a bit more and submit a proper patch if this works.

and decided to wait for a proper patch from you.  I was thinking
the delay meant there was something you needed to work further...

I've just tested your proper patch and it worked across v4.3.2 (of
Ubuntu 22.04) and V6.2.1 (of Fedora 39), among others.

Many thanks,
Akira

> 
> 
> Vegard

  reply	other threads:[~2024-02-15 11:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14 23:25 [PATCH] docs: Only load the translations extension for HTML output Jonathan Corbet
2024-02-15  2:43 ` Akira Yokosawa
2024-02-15  6:22   ` Vegard Nossum
2024-02-15 11:10     ` Akira Yokosawa [this message]
2024-02-15 11:24       ` Vegard Nossum
2024-02-15 16:22   ` 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=d34e3dce-0a16-48fc-b3dd-e83ff3568baa@gmail.com \
    --to=akiyks@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=vegard.nossum@oracle.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).