unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: karl@freefriends.org (Karl Berry)
To: timh@insightful.com
Cc: bug-gnu-emacs@gnu.org
Subject: Re: latex mode, nexted subscripts are unreadable
Date: Wed, 12 Sep 2007 13:12:33 -0500	[thread overview]
Message-ID: <200709121812.l8CICXf18901@f7.net> (raw)

Hi Tim,

Thanks for the report.

    the nested suscripts are visible, but are still too tiny for comfort.
    And they're not clearly visible - the gray letters end up with most of
    the pixels light gray and a few of them darker.

Unfortunately neither I nor Juri were able to reproduce this on our
(non-Windows) systems.  

Is there an Emacs developer who works on Windows who could look into this?

    Is there a way to set a minimum font size for suscripts?

Looking at tex-mode.el, it seems that faces named `subscript' and
`superscript' are used for this.  By default, they are defined like this
(both are just the same except for the name):

    (defface subscript
      '((t :height 0.8)) ;; :raise -0.3
      "Face used for subscripts."
      :group 'tex)

The :height is presumably what makes it proportional to the next "level"
up.  So perhaps it would work to override these definitions by changing
those faces -- using customize is probably easiest -- to use an absolute
font size.

Best,
Karl




             reply	other threads:[~2007-09-12 18:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 18:12 Karl Berry [this message]
2007-09-12 22:34 ` latex mode, nexted subscripts are unreadable Jason Rumney
2007-09-13  0:48   ` Tim Hesterberg
2007-09-13 15:03     ` Drew Adams
2007-09-26  7:41   ` Glenn Morris
2007-09-12 23:40 ` Tim Hesterberg
2007-09-14  0:24   ` Karl Berry
2007-09-14 16:47     ` Tim Hesterberg
  -- strict thread matches above, loose matches on Subject: below --
2007-09-06 23:21 Tim Hesterberg

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200709121812.l8CICXf18901@f7.net \
    --to=karl@freefriends.org \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=timh@insightful.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).