From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/4266 Path: main.gmane.org!not-for-mail From: Uwe Koloska Newsgroups: gmane.comp.tex.context Subject: Re: Problem with AER-Font : =?iso-8859-1?q?=DF=20becomes=20SS?= Date: Sun, 4 Mar 2001 23:08:03 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <01030423080301.00686@bilbo> References: <5.0.2.1.2.20010304130201.00a705c8@pop.btx.dtag.de> 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 1035394946 24268 80.91.224.250 (23 Oct 2002 17:42:26 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:42:26 +0000 (UTC) Original-To: ntg-context@ntg.nl In-Reply-To: <5.0.2.1.2.20010304130201.00a705c8@pop.btx.dtag.de> Xref: main.gmane.org gmane.comp.tex.context:4266 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:4266 Am Sonntag, 4. März 2001 13:34 schrieb Robert F. Beeger: > Hi! > > I'm using now the AER-Font to make my hyphenation for german words work. > All seemed to work fine until a more careful reading of my text > > Changing my file this way : > \mainlanguage[de] > \language[de] > > \setupbodyfont[aer, 10pt] > > \input xhyphen what is this supposed to do? I don't have such a file ... > \useencoding[win] yes, that' the right thing to do (R) ;-) > \starttext > äÄ üÜ öÖ ß > \stoptext > > seems to do it, but it doesn't look right to me to change the encoding > after the hyphenation is done. where do you do the hyphenation??? > And what do I need \useencoding[win] for. It is for changing the _input_encoding! It's a little bit confusing that there is no differentiation between input and output encoding. "ec" is an output encoding used to map internal codes to external ones. "pro" is a special case, cause it is needed for protruding (that is something I don't understand in depth ...). "win" is an input encoding. So maybe "\input xhyphen" uses some characters that are remapped by "win". Though "win" is a name I don't like ;-) it now is the right encoding when "mostly ansi 8859-1" is meant. I thought that the AER-Font > would contain the Umlauts and the ß so that there be no need to > map them again. Is there a mistake in the mapping of the ß in the > AER-Font? Yes, if you think from the ansi 8859-1 direction. The characters in AER are mapped with the T1 encoding. An if you think about the presentation of characters for computers -- they don't see the glyphs, they only see a number, and a convention (an encoding) is used to associate glyphs with this number -- you may finally be able to understand the problem: You enter your text in a specific encoding (for nearly all western encodings the codes for the ASCII section are the same, so an "A" is an "A" is an "A" ;-)) and the fonts you use have another one. Hope this helps Uwe -- mailto:koloska@rcs.urz.tu-dresden.de http://rcswww.urz.tu-dresden.de/~koloska/ -- -- right now the web page is in german only but this will change as time goes by ;-)