From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>
Cc: Randy Dunlap <rdunlap@infradead.org>
Subject: Re: Adding warning icon to warning admonitions?
Date: Sat, 6 Jan 2024 19:43:44 +0700 [thread overview]
Message-ID: <ZZlLAOm1g_R01VGj@archie.me> (raw)
In-Reply-To: <87edev3jya.fsf@meer.lwn.net>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
On Fri, Jan 05, 2024 at 07:59:09AM -0700, Jonathan Corbet wrote:
> Bagas Sanjaya <bagasdotme@gmail.com> writes:
>
> > For the icon itself, the approach is to use Font Awesome [2] (many other doc
> > sites that uses Sphinx also do that due to site theme they use but Alabaster
> > theme don't use the icon, hence this question). I personally prefer regular
> > icon variant (like in TT), but alas it is in non-free PRO plan (and only
> > solid variant is free and that is what Sphinx themes using).
> >
> > Does adding warning icon like above idea make sense for the kernel docs? And
> > does it require non-trivial (complex) changes to Alabaster theme?
>
> It can probably be done with a bit of CSS tweaking. I don't really like
> the idea of requiring the installation of another font to build the
> docs, though, and Font Awesome looks like it could bring in licensing
> issues of its own - that's not clear from the site at all.
OK, thanks!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-01-06 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 14:28 Adding warning icon to warning admonitions? Bagas Sanjaya
2024-01-05 14:59 ` Jonathan Corbet
2024-01-05 18:12 ` Vegard Nossum
2024-01-06 13:02 ` Bagas Sanjaya
2024-01-06 12:43 ` Bagas Sanjaya [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=ZZlLAOm1g_R01VGj@archie.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox