From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
linux-doc@vger.kernel.org,
"Mauro Carvalho Chehab" <mchehab@kernel.org>
Subject: Re: [PATCH] docs: automarkup: Mark up undocumented entities too
Date: Wed, 4 Jun 2025 09:37:07 +0200 [thread overview]
Message-ID: <20250604093653.7e2b88e5@foz.lan> (raw)
In-Reply-To: <87iklcjul5.fsf@trenco.lwn.net>
Em Tue, 03 Jun 2025 17:04:06 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> Jonathan Corbet <corbet@lwn.net> writes:
>
> > I wonder why they used a border rather than the text-decoration that is
> > there for exactly that purpose? I'm inclined to change the CSS to get
> > reliable underlining for everybody.
>
> Having played with this a bit, I'm guessing they went with the border
> because the text-decoration underline gets mixed up with underscores in
> function names, while the border sits below the underscore.
>
> Assuming we want to preserve that behavior, tossing in a line like:
>
> border-bottom-width: 2px;
>
> makes those underlines (that I never even knew existed :) visible. So
> maybe that's the approach to take?
What I suspect is that this could be related to your monitor's DPI,
and eventually to WM scaling. When you used a larger size, it became
visible.
I would override CSS and replace a.reference to disable border and
enable text decoration, as this is probably more portable.
Still, I think it is worth to have separate CSS classes for xref
and broken xref, as if one wants to do a different decoration,
that would be possible.
>
> Thanks,
>
> jon
Thanks,
Mauro
next prev parent reply other threads:[~2025-06-04 7:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 17:20 [PATCH] docs: automarkup: Mark up undocumented entities too Jonathan Corbet
2025-06-03 19:44 ` Nícolas F. R. A. Prado
2025-06-03 21:12 ` Jonathan Corbet
2025-06-03 21:35 ` Nícolas F. R. A. Prado
2025-06-03 22:47 ` Jonathan Corbet
2025-06-03 23:04 ` Jonathan Corbet
2025-06-04 7:37 ` Mauro Carvalho Chehab [this message]
2025-06-04 13:19 ` Nícolas F. R. A. Prado
2025-06-04 14:22 ` Jonathan Corbet
2025-06-03 21:27 ` Mauro Carvalho Chehab
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=20250604093653.7e2b88e5@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nfraprado@collabora.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.