From: Taco Hoekwater <taco.hoekwater@wkap.nl>
Subject: Re: <ATTN task force> LaTeX's T1 encoding / LaTeX PS fonts
Date: Sat, 17 Jul 1999 14:51:55 +0200 (W. Europe Daylight Time) [thread overview]
Message-ID: <14224.31851.720000.122268@PC709> (raw)
In-Reply-To: <378FC6CF.8270E083@wxs.nl>
>>>>> "HH" == Hans Hagen <pragma@wxs.nl> writes:
HH> Erik Frambach wrote:
>> Until now always had problems with Times: first ConTeXt seems to
>> insist on using tir.tfm, etc., then I get problems with either
>> missing accents or funny
HH> Hm. One can use filemapping to use other names, so it is under
HH> your control. Currently the method is:
...
The important thing about this patch is/was the enco-ec.tex
file. After Hans & I have sorted out a few minor glitches, it will
move into the core distrib.
Perhaps we should do one for (each of the) (silly, because they are
all slighly different from eachother) 7-bit tex text encodings as
well, getting rid of the hardcoded plain stuff alltogether
>> But never everything correct at the same time.
HH> This is an encoding issue and related to the previous. We use
HH> times a lot (tir files) and never had those problems, but I think
HH> your problem could have been due to missing texnansi tfm
HH> files. Taco once suggested to set up an archive for this (if only
Probably caused by the fact that there were other,older versions of
tir.tfm that were not re-encoded at all but 'raw': using
AdobeStandardEncoding, which is nearly useless for typesetting.
HH> because texnansi is a rather good encoding). One reason for
HH> using the tir ones is (was) that I dislike those (sometimes even)
HH> changing berry names, and prefer originals. It's also the reason
HH> why I have my own mapping files (taco, should we also provide a
HH> map file?).
Not for this berry stuff, that is part of any standard tex distrib.
And since you & me are probably the only people that use and have the
texnansi tfms, I don't see a real reason yet. If and when we create a
distribution for texnansi tfms, we definately should. But I am not in
a hurry to do that...
>> Maybe I'm stupid, but anyway I for one am VERY happy to see that
>> this new method actually WORKS for me.
HH> Good to hear that!
HH> Since the names in font-ber change now, we must make sure we make
HH> the right choices once and for all (that is: taco makes the
HH> choices -).
This is why I asked for the names for the other fonts. At least the
base35 (but preferably all of the PS3 ones) should be in there and
correctly named. But I no longer have those files (trying to cut down
hd space), so I depend on other people to tell me what they are called
(the proper psnfss name for the 8t encoded version, that is).
HH> Some time ago I got some baskerville fonts needed to
HH> typeset some UKTUG stuff, and ended up with 5 subdir with 5 sets
HH> of tfm files and I never could sort out which one to use,
HH> especially because the names in the map files were yet another
HH> set.
Isnt life fun?
Taco
next prev parent reply other threads:[~1999-07-17 12:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-16 14:26 Erik Frambach
1999-07-16 23:57 ` Hans Hagen
1999-07-17 12:51 ` Taco Hoekwater [this message]
1999-07-17 17:34 ` Hans Hagen
1999-07-16 15:09 Taco Hoekwater
1999-07-16 16:38 ` Taco Hoekwater
1999-07-17 17:26 ` Siep Kroonenberg
1999-07-18 9:15 ` Taco Hoekwater
1999-07-21 9:53 ` Matthew Baker
1999-07-16 15:21 Karsten Tinnefeld
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=14224.31851.720000.122268@PC709 \
--to=taco.hoekwater@wkap.nl \
/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).