#96 default menu font too big

release
closed-duplicate
nobody
Program (402)
1
2002-06-21
2001-11-26
ariese
No

A few weeks ago the default (menu) font has been
changed in nedit.c from

-*-helvetica-medium-r-normal-*-12-*-*-*-*-*-*

to

-*-helvetica-medium-r-normal-*-*-120-*-*-*-*-*

This changed the font to a much larger one (at least on
an SGI). I'm not a font expert, but it seems to me that
the correct value should be

-*-helvetica-medium-r-normal-*-*-120-75-75-*-*-*

Any ideas?

Discussion

  • Scott Tringali

    Scott Tringali - 2001-11-26

    Logged In: YES
    user_id=11321

    [tringali]

    This won't work because nothing guarantees a certain DPI
    font will be available on a server. Until then, I'd suggest
    just changing your default font with an X resource.

    What might make more sense is changing it to a ten *point*
    font. This is more in the spirit of the original font
    specification.

    Trying to find a single font that will work on all systems
    and please everybody is pointless. It doesn't exist. What
    works on one system is ugly on others, and it's all
    subjective anyway.

    The original change was made to avoid badly scaled (chunky)
    fonts on certain X servers. So, if we have a choice of
    badly scaled fonts versus too-big fonts, I'd prefer to
    choose too-big.

    A solution that works and pleases everyone will not be to
    change the default to hardcoded "font X", but require a far
    trickier solution. We'd need some sort of smart handling
    that uses the system default font if it's available, but
    falls back on a reasonable default if there is none. The
    trick is supporting both systems that have support for Motif
    installed and those that don't.

     
  • Scott Tringali

    Scott Tringali - 2001-11-26
    • milestone: 103147 --> release
    • priority: 5 --> 1
     
  • Paul Douglas Welton

    Logged In: YES
    user_id=288126

    I have used nedit on Linux (Red Hat 7.0) for over a year.
    On upgrading to Red Hat 7.2, nedit started to display the
    menus with all characters as a square symbol, making the
    tool unusable.

    I devised a workaround: "nedit -xrm 'nedit*fontList: XYZ'"
    causes the message "Cannot convert string "XYZ" to type
    FontStruct" to be printed, and then the editor comes up and
    works normally. If XYZ is replaced by the value given above
    (containing 120) then the unreadable characters appear, but
    with 12, the normal text is restored, but the message about
    "Cannot convert string" returns.

    From this behavior, I infer that it is only working because
    the previous default font was not recognised, so it used a
    default font that worked. The change to 120 made the
    default font recognised in some way, and exposed the
    problem.

    You will gather from this description that I am an
    unsophisticated user,
    but I have entered this report because upgrading a RedHat
    distribution is likely to be a common operation, and the
    problem is difficult for the user to fix or even workaround.
    I have so far been unable to ammend the .nedit file to
    fix the problem, although nedit is able to correctly store
    and recover preferences set using the menu options in this
    file.

     
  • Scott Tringali

    Scott Tringali - 2002-02-08

    Logged In: YES
    user_id=11321

    Thanks for your comment. The blank-square thing is covered
    under another bug report here. That's a good workaround to
    know.

     
  • Scott Tringali

    Scott Tringali - 2002-02-08
    • status: open --> open-duplicate
     
  • Scott Tringali

    Scott Tringali - 2002-02-12

    Logged In: YES
    user_id=11321

    The other bug report covering the 'block' problem is here:

    http://sourceforge.net/tracker/index.php?
    func=detail&aid=434383&group_id=11005&atid=111005

     
  • Scott Tringali

    Scott Tringali - 2002-06-21

    Logged In: YES
    user_id=11321

    Fixed in 5.3.

     
  • Scott Tringali

    Scott Tringali - 2002-06-21
    • status: open-duplicate --> closed-duplicate
     

Log in to post a comment.