Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.1830); Fri, 1 Dec 2006 17:33:51 +0100 Received: by mail.proteosys.com (8.13.6/8.13.4) with ESMTP id kB1GXkwN031402 for ; Fri, 1 Dec 2006 17:33:46 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay2.uni-heidelberg.de (8.12.10/8.12.10) with ESMTP id kB1GNAwo028920; Fri, 1 Dec 2006 17:23:10 +0100 (MET) Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id kAUN21Uo027421; Fri, 1 Dec 2006 17:23:04 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 14.3) with spool id 1291623 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 1 Dec 2006 17:23:04 +0100 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id kB1GN4YY016607 for ; Fri, 1 Dec 2006 17:23:04 +0100 Received: from hygeia.frycomm.com (hygeia.frycomm.com [65.167.125.6]) by relay2.uni-heidelberg.de (8.12.10/8.12.10) with ESMTP id kB1GMlwo028795 for ; Fri, 1 Dec 2006 17:22:50 +0100 (MET) Received: from [192.168.21.139] (charon.frycomm.com [65.167.125.1]) by hygeia.frycomm.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id kB1GMjSs027221 for ; Fri, 1 Dec 2006 11:22:45 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v752.2) References: Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.752.2) Message-ID: <142F6D60-2BFD-4CF9-9B5C-EFD7FFBED00C@frycomm.com> Date: Fri, 1 Dec 2006 11:22:44 -0500 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: William Adams Subject: Re: The Next Font Selection Scheme To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: Precedence: list X-ProteoSys-SPAM-Score: -2.339 () AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.57 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 01 Dec 2006 16:33:52.0753 (UTC) FILETIME=[7CC5BE10:01C71566] Status: R X-Status: X-Keywords: X-UID: 4998 On Dec 1, 2006, at 10:24 AM, J.Fine wrote: > In web pages, CSS is commonly used for 'font selection' > and if required the endcoding can be Unicode. > I'd find it helpful to know to what degree CSS and > Unicode would solve font selection problems for > printed pages. Well, Unicode as implemented in XeTeX (and other TeX-variants) is solved for most problems. CSS font selection is pretty primitive --- the only thing it adds AFAICT would be ``Generic font families'' (which map nicely to default) adding ``cursive'' and ``fantasy''. > Excluding mathematics, of course. That has its > own issues. > > I'm expecting a relatively short list of things > that can't be done, or done only with difficulty. Things which CSS font selection doesn't encompass: width optical size (as opposed to physical --- I left this out of my list) font features such as swash and contextual ligatures numberstyles They do have a nice numbering scheme for weight though (100--900) which could be adapted --- there's no reason this couldn't be a superset of CSS --- that's a very good idea and also use the numbering scheme for widths. William -- William Adams senior graphic designer Fry Communications This email message and any files transmitted with it contain information which is confidential and intended only for the addressee(s). If you are not the intended recipient(s), any usage, dissemination, disclosure, or action taken in reliance on it is prohibited. The reliability of this method of communication cannot be guaranteed. Email can be intercepted, corrupted, delayed, incompletely transmitted, virus-laden, or otherwise affected during transmission. Reasonable steps have been taken to reduce the risk of viruses, but we cannot accept liability for damage sustained as a result of this message. If you have received this message in error, please immediately delete it and all copies of it and notify the sender.