unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Jason Rumney <jasonr@gnu.org>
Cc: Reiter.Joachim@web.de, bug-gnu-emacs@gnu.org,
	Richard Stallman <rms@gnu.org>
Subject: Re: [Reiter.Joachim@web.de: Failure to show "German Umlaute"]
Date: Sat, 17 Nov 2007 17:24:16 +0100	[thread overview]
Message-ID: <v91waoyh5b.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <473EE3A9.7060302@gnu.org> (Jason Rumney's message of "Sat, 17 Nov 2007 12:50:49 +0000")

On Sat, Nov 17 2007, Jason Rumney wrote:

> It's not clear to me what the bug is. The umlauts are clearly visible in
> both screenshots. Is the user complaining about the fact that some
> characters get clipped 

Yes.  E.g. in <http://www.hobbyecke-pc.de/images/screensh2.png> the
text says:

,----
|   wä wö mä mö
| 
| In the letters "w" and "m", the right column of pixels is not
| displayed.
| 
|   wa wo ma mo
`----

If the iso-characters "ä" and "ö" are replaced by their ASCII
"counterparts" ("a" and "o") the letters "w" and "m" are displayed
correctly.

> when Cleartype is enabled due to Windows supplying incorrect metrics
> for the font? If so, this is documented in etc/PROBLEMS.

Joachim, does turning of "ClearType" solve the problem?

,----[ etc/PROBLEMS: Known problems with the MS-Windows port of Emacs 22.1 ]
| When "ClearType" method is selected as the "method to smooth edges of
| screen fonts" (in Display Properties, Appearance tab, under
| "Effects"), there are various problems related to display of
| characters: 2-pixel trace is left behind when moving overlays, bold
| fonts can be hard to read, small portions of some characters could
| appear chopped, etc.  This happens because, under ClearType,
| characters are drawn outside their advertised bounding box.  Emacs 21
| disabled the use of ClearType, whereas Emacs 22 allows it and has some
| code to enlarge the width of the bounding box.  Apparently, this
| display feature needs more changes to get it 100% right.  A workaround
| is to disable ClearType.
`----

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  reply	other threads:[~2007-11-17 16:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1IsspP-0003Yd-0g@fencepost.gnu.org>
2007-11-17 11:44 ` [Reiter.Joachim@web.de: Failure to show "German Umlaute"] Reiner Steib
2007-11-17 12:50   ` Jason Rumney
2007-11-17 16:24     ` Reiner Steib [this message]
2007-11-17 16:50       ` Jason Rumney
2007-11-17 17:20         ` Eli Zaretskii
2007-11-18 19:36 Joachim Reiter
  -- strict thread matches above, loose matches on Subject: below --
2007-11-18 19:39 Joachim Reiter
2007-11-19 14:20 ` Joachim Reiter
     [not found] <mailman.3755.1195415548.18990.bug-gnu-emacs@gnu.org>
2007-11-18 20:17 ` Sven Joachim

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=v91waoyh5b.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=Reiter.Joachim@web.de \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=jasonr@gnu.org \
    --cc=rms@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.
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).