From: Uwe Koloska <uwe.koloska@mailbox.tu-dresden.de>
Subject: Re: Problem with AER-Font : ß becomes SS
Date: Sun, 4 Mar 2001 23:08:03 +0100 [thread overview]
Message-ID: <01030423080301.00686@bilbo> (raw)
In-Reply-To: <5.0.2.1.2.20010304130201.00a705c8@pop.btx.dtag.de>
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 ;-)
next prev parent reply other threads:[~2001-03-04 22:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-04 12:34 Robert F. Beeger
2001-03-04 22:08 ` Uwe Koloska [this message]
2001-03-05 7:31 ` Robert F. Beeger
2001-03-05 10:45 ` Uwe Koloska
2001-03-06 10:12 ` Robert F. Beeger
2001-03-06 22:39 ` Uwe Koloska
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01030423080301.00686@bilbo \
--to=uwe.koloska@mailbox.tu-dresden.de \
/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.
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 NNTP newsgroup(s).