Linux Documentation
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Rito Rhymes <rito@ritovision.com>,
	Daniel Lundberg Pedersen <dlp@qtec.com>,
	linux-doc@vger.kernel.org, linux-media@vger.kernel.org,
	Rito Rhymes <rito@ritovision.com>
Subject: Re: Bad wrapping in some tables
Date: Fri, 10 Jul 2026 09:34:26 -0600	[thread overview]
Message-ID: <87bjcen9j1.fsf@trenco.lwn.net> (raw)
In-Reply-To: <DJUP0UXLLHJ0.3P121A982R9TP@ritovision.com>

"Rito Rhymes" <rito@ritovision.com> writes:

> Reason 2: the real culprit here is this:
>
> Table mobile responsiveness in general in the Linux kernel
> documentation is systemically pathological.

I honestly have to question how important that is to us.  How many
people are really trying to make use of the kernel documentation on
small-screen devices?  This is the kind of information you need when you
have editor and terminal windows open.

Making small screens work better is fine on its own, but I don't think
it should be done at the cost of proper rendering on the sort of devices
that developers actually use.  There are limits to which we want to
develop and maintain our own custom theme for a use case that, I
believe, is pretty rare.

Thanks,

jon

      parent reply	other threads:[~2026-07-10 15:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 16:39 Bad wrapping in some tables Daniel Lundberg Pedersen
2026-07-07 17:14 ` Manuel Ebner
2026-07-07 17:36 ` Jonathan Corbet
2026-07-10  6:55   ` Rito Rhymes
2026-07-10  8:11     ` Hans Verkuil
2026-07-10  8:42       ` Mauro Carvalho Chehab
2026-07-10 12:38     ` Daniel Lundberg Pedersen
2026-07-10 13:17       ` Mauro Carvalho Chehab
2026-07-10 15:34     ` Jonathan Corbet [this message]

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=87bjcen9j1.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=dlp@qtec.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=rito@ritovision.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