From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/8140 Path: main.gmane.org!not-for-mail From: Eckhart =?ISO-8859-1?Q?Guth=F6hrlein?= Newsgroups: gmane.comp.tex.context Subject: Re: Umlaut vs. diaresis Date: Wed, 05 Jun 2002 20:08:45 +0200 Sender: owner-ntg-context@let.uu.nl Message-ID: <1023300526.507.13.camel@hades> References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1035398569 25043 80.91.224.250 (23 Oct 2002 18:42:49 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 18:42:49 +0000 (UTC) Cc: ntg-context@ntg.nl Original-To: mari.voipio@iki.fi, Hans Hagen Xref: main.gmane.org gmane.comp.tex.context:8140 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:8140 Am Die, 2002-05-14 um 12.24 schrieb mari.voipio@iki.fi: > The result of the above is that we usually place the dots (diaeresis) or > rings quite close to the rest of the character as they are parts of the > same glyph. In ConTeXt the closest presentation of this seems to be, funny > enough, \aumlaut and \oumlaut while there isn't any fix to å (a ring); /aa > (or å directly from my Finnish keyboard) really looks odd in the ConTeXt > output as the ring is very thin and quite high up, looks a bit like it is > about to fly away. :-) I also wondered about the odd appearance of \Aring (when using my favorite unit, \Angstrom). The reason is, as far as I have traced it, that context defaults to the ae fonts. The respective glyphs in the ec fonts look much better. I have been absent from ec / type1 issues for some time, so a question from my part: Are the freely available type1 versions of these fonts mature enough and included in the major distributions, so they could be used instead of the ae fonts by default? If so, I think this should be considered. Eckhart