From: Gavin Smith <gavinsmith0123@gmail.com>
To: Gnulib bugs <bug-gnulib@gnu.org>
Cc: Steve Ward <planet36@gmail.com>, Texinfo <bug-texinfo@gnu.org>,
50116@debbugs.gnu.org
Subject: Fwd: bug#50116: Text on GNU grep webpage far too big
Date: Fri, 20 Aug 2021 18:10:41 +0100 [thread overview]
Message-ID: <CAKPWYQ3hfjMpyTZEdMUsCZqTyJOP0ERbF8cZz1pxvyYKO-GqXg@mail.gmail.com> (raw)
In-Reply-To: <CA+XvV5Gy+avV52MYO4VQQ1srqqTdo2DcUpaUCUAV37xXUJT9Sg@mail.gmail.com>
Does anybody have access to
https://www.gnu.org/software/gnulib/manual.css and could the CSS lines
mentioned below removed? These CSS lines would be a problem with any
Texinfo manual built with Texinfo 6.8 due to changes in the structure
of the HTML (enclosing an entire section in <div class="section">
rather than just the section heading).
---------- Forwarded message ---------
From: Steve Ward <planet36@gmail.com>
Date: Thu, Aug 19, 2021 at 12:56 PM
Subject: Re: bug#50116: Text on GNU grep webpage far too big
To: Gavin Smith <gavinsmith0123@gmail.com>
Cc: <50116@debbugs.gnu.org>
On Thu, Aug 19, 2021 at 2:12 AM Gavin Smith <gavinsmith0123@gmail.com> wrote:
>
> https://www.gnu.org/software/grep/manual/grep.html
>
> This documentation is not usable because the text is far too big. I assume
> it is being enlarged with a CSS file.
>
>
>
In the manual.css file [0], commenting out the font-size property in
these blocks makes the page look normal to me.
.settitle, .top, .chapter
/*font-size: 250%;*/
.section, .subsection, .subsubsection
/*font-size: 150%; */
[0] <https://www.gnu.org/software/gnulib/manual.css>
next parent reply other threads:[~2021-08-20 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210819061114.GA12892@mintstar>
[not found] ` <CA+XvV5Gy+avV52MYO4VQQ1srqqTdo2DcUpaUCUAV37xXUJT9Sg@mail.gmail.com>
2021-08-20 17:10 ` Gavin Smith [this message]
2021-08-20 19:37 ` bug#50116: Text on GNU grep webpage far too big Paul Eggert
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKPWYQ3hfjMpyTZEdMUsCZqTyJOP0ERbF8cZz1pxvyYKO-GqXg@mail.gmail.com \
--to=gavinsmith0123@gmail.com \
--cc=50116@debbugs.gnu.org \
--cc=bug-gnulib@gnu.org \
--cc=bug-texinfo@gnu.org \
--cc=planet36@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).