X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["666" "Wed" "26" "January" "1994" "20:17:04" "+0100" "Julio Sanchez" "jsanchez@GMV.ES" "<199401262032.AA14853@mail.cs.tu-berlin.de>" "19" "Re: Default fontencodings" "^Date:" nil nil "1" "1994012619:17:04" "Default fontencodings" (number " " mark " Julio Sanchez Jan 26 19/666 " thread-indent "\"Re: Default fontencodings\"\n") "<01H84XRKWADA000K9X@esgbox.ub.es>"]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/24.6.93) id AA10286; Wed, 26 Jan 94 21:34:12 +0100 Received: from mail.cs.tu-berlin.de by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/03.06.93) id AA29288; Wed, 26 Jan 94 21:32:10 +0100 Received: from tubvm.cs.tu-berlin.de by mail.cs.tu-berlin.de with SMTP id AA14853 (5.65c8/IDA-1.4.4(mail.m4[1.12]) for <@MAIL.CS.TU-BERLIN.DE:Schoepf@SC.ZIB-BERLIN.DE>); Wed, 26 Jan 1994 21:32:08 +0100 Message-Id: <199401262032.AA14853@mail.cs.tu-berlin.de> Received: from TUBVM.CS.TU-BERLIN.DE by tubvm.cs.tu-berlin.de (IBM VM SMTP V2R2) with BSMTP id 5263; Wed, 26 Jan 94 21:32:10 +0200 Received: from VM.URZ.UNI-HEIDELBERG.DE (NJE origin MAILER@DHDURZ1) by TUBVM.CS.TU-BERLIN.DE (LMail V1.2a/1.8a) with BSMTP id 5262; Wed, 26 Jan 1994 21:32:10 +0200 Received: from VM.URZ.UNI-HEIDELBERG.DE (NJE origin LISTSERV@DHDURZ1) by VM.URZ.UNI-HEIDELBERG.DE (LMail V1.2a/1.8a) with BSMTP id 2470; Wed, 26 Jan 1994 21:31:42 +0000 Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <01H84XRKWADA000K9X@esgbox.ub.es> (message from Dean Ayres on 26 Jan 1994 10:17:08 +0000 (GMT)) Date: Wed, 26 Jan 1994 20:17:04 +0100 From: Julio Sanchez Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: Default fontencodings Status: R X-Status: X-Keywords: X-UID: 1316 Date: 26 Jan 1994 10:17:08 +0000 (GMT) From: Dean Ayres At the LaTeX user interface level, aren't the T1 encoded dc fonts supposed to appear indistinguishable from the OT1 encoded cm fonts? The DC fonts left out the ?` and !` ligatures or so it seems. Since there are no user-level macros that reach them and since the character moved from OT1 to T1, I can tell them apart very well. This is not a fault of T1 per se, but since you raised the DC topic... Last time I checked, DC fonts still had this wrong. If I remember correctly, the PostScript fonts with T1 encoding are OK. Moreover, hyphenation is different. Julio