public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "skannan at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/50642] onlinedocs formated text too small to read
Date: Thu, 18 Apr 2013 09:40:00 -0000	[thread overview]
Message-ID: <bug-50642-4-6jlRXnjAPA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50642-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50642

Shakthi Kannan <skannan at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |skannan at redhat dot com

--- Comment #7 from Shakthi Kannan <skannan at redhat dot com> 2013-04-18 09:40:36 UTC ---
'Small' can mean different things depending on the context. It can refer to a
simple example, or something that is tiny.

On Mozilla Firefox 16.0.2, the 'smallexample' is indeed difficult to read. 

Please change the font size to normal. If it appears similar to the text, a
different font family can be used.


  parent reply	other threads:[~2013-04-18  9:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06 22:06 [Bug web/50642] New: " jg at jguk dot org
2011-10-07  0:21 ` [Bug web/50642] " paolo.carlini at oracle dot com
2011-10-07  0:49 ` redi at gcc dot gnu.org
2011-10-07  8:24 ` gjl at gcc dot gnu.org
2011-10-07 16:34 ` schwab@linux-m68k.org
2011-10-07 17:18 ` gjl at gcc dot gnu.org
2011-11-12 23:30 ` jg at jguk dot org
2013-04-18  9:40 ` skannan at redhat dot com [this message]
2013-04-18 10:02 ` manu at gcc dot gnu.org
2013-05-06 10:33 ` skannan at redhat dot com
2013-07-01 10:46 ` jg at jguk dot org
2013-07-01 10:51 ` skannan at redhat dot com

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=bug-50642-4-6jlRXnjAPA@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).