From: Uwe Koloska <uwe.koloska@mailbox.tu-dresden.de>
Subject: Re: and again the szlig
Date: Wed, 21 Mar 2001 19:54:45 +0100 [thread overview]
Message-ID: <01032119544500.02716@bilbo> (raw)
In-Reply-To: <3.0.6.32.20010321152721.016f71d0@server-1>
Am Mittwoch, 21. März 2001 15:27 hast du geschrieben:
> At 11:45 AM 3/21/01 +0100, Uwe Koloska wrote:
> >Hello,
> >
> >I just tried the new beta 2001.3.12 but am not able to get an szlig.
> > The following input file has all umlauts correct but not the szlig:
> >
> >The ß gives "SS" ...
>
> depending on the *encoding* used for the times fonts, (ec or texnansi),
> you now need to take a look at enco-ec.tex and enco-ans.tex
Yes, this is the part of the encoding thingy that I have (mostly)
understand ;-)
ssharp in latin1 := 223
ssharp on my computer := 223 (veryfied)
regi-win.tex: 223 -> \ssharp
enco-ec.tex: ssharp -> 223
[long explanation deleted]
I have found the source of the error. ec-encoding is the encoding
specified at the Cork TUG Meeting and because the glyphs used for this
encoding are not accessible with the adobe standard encoding, there is
TeXBase1 Encoding that is used for the raw fonts. From TeXBase1 TeXandAnsi
is derived and has some advantages. Long words for short:
Latin1 Base1 Cork (aka ec)
ß 223 223 255
So the enco-ec has to be changed to
\definecharacter ssharp 255
\definecharacter Ssharp 223
So the problem was mine, correcting a bug in enco-ec the wrong way ...
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 ;-)
prev parent reply other threads:[~2001-03-21 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 10:45 Uwe Koloska
2001-03-21 14:27 ` Hans Hagen
2001-03-21 18:54 ` Uwe Koloska [this message]
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=01032119544500.02716@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).