All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Daniel Lundberg Pedersen <dlp@qtec.com>
Cc: Rito Rhymes <rito@ritovision.com>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: Bad wrapping in some tables
Date: Fri, 10 Jul 2026 15:17:35 +0200	[thread overview]
Message-ID: <20260710151735.40aa2941@localhost> (raw)
In-Reply-To: <82c74030-88c6-4bf2-ae76-41c2a68ced61@qtec.com>

On Fri, 10 Jul 2026 14:38:06 +0200
Daniel Lundberg Pedersen <dlp@qtec.com> wrote:

> Hi
> 
> On 10/07/2026 08:55, Rito Rhymes wrote:
> > I just got caught up to speed, reviewing the links, the regression, the
> > prior state and other relevant context.
> > 
> > Daniel, thanks for pointing out the regression. As Jon said, it's
> > always good to inform the author of the patch, and I'd have been happy
> > to discuss and test out solutions with you.  
> 
> Sorry about that, I'll remember that for next time.
> 
> [...]
> > 
> > The best solution:
> > Make targeted changes to the tables to make them fundamentally behave
> > better on smaller screen sizes.
> > 
> > I began this effort with:
> > [PATCH v3] docs: wrap generated tables to contain small-screen overflow
> > 
> > Jon hadn't followed up after testing out the fix with CSS and my
> > explaining why the wrapper was the better approach, because it prevented
> > regressions. That fix is a start, but more would need to be done.
> > 
> > If Daniel is willing to help test out table fixes and provide examples
> > of regressions, and if Jon has the bandwidth to review my patch
> > submissions to improve the tables, I am willing to tackle this systemic
> > issue, which will result in this issue being resolved as well.  
> 
> I don't mind testing some stuff if you want me to, but as Hans mentions 
> the media docs is full of tables which have these issues, from a quick
> check, almost all sub-pages of the Function Reference are affected:
> 
> https://www.kernel.org/doc/html/latest/userspace-api/media/v4l/user-func.html

On media, I guess the more complex tables with long widths are the pixfmt 
ones like those:

	https://www.kernel.org/doc/html/latest/userspace-api/media/v4l/pixfmt-rgb.html
	https://www.kernel.org/doc/html/latest/userspace-api/media/v4l/pixfmt-packed-yuv.html

It is a good place to check for issues like that.

Please see the patch I submitted:

	https://lore.kernel.org/linux-doc/1950557405f1150acb1de50de1801f2413223b87.1783673996.git.mchehab+huawei@kernel.org/

It moves width support at the html output from previous
millennium SVGA-resolutions era to modern age.

-- 
Thanks,
Mauro

  reply	other threads:[~2026-07-10 13:17 UTC|newest]

Thread overview: 11+ 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-12 11:19         ` Rito Rhymes
2026-07-10 12:38     ` Daniel Lundberg Pedersen
2026-07-10 13:17       ` Mauro Carvalho Chehab [this message]
2026-07-10 15:34     ` Jonathan Corbet
2026-07-12 10:45       ` Rito Rhymes

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=20260710151735.40aa2941@localhost \
    --to=mchehab+huawei@kernel.org \
    --cc=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 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.