Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by h1439878.stratoserver.net (8.14.2/8.14.2/Debian-2build1) with ESMTP id s4K9a1hp026005 for ; Tue, 20 May 2014 11:36:02 +0200 Received: from relay.uni-heidelberg.de ([129.206.100.212]) by mx-ha.gmx.net (mxgmx105) with ESMTPS (Nemesis) id 0MYtZ9-1WH74S1Ax9-00VeQJ for ; Tue, 20 May 2014 11:35:56 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id s4K9VNpx026866 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 May 2014 11:31:23 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id s4JM1L2A006797; Tue, 20 May 2014 11:31:22 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 11019162 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 20 May 2014 11:31:22 +0200 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id s4K9VMGD018878 for ; Tue, 20 May 2014 11:31:22 +0200 Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lp0010.outbound.protection.outlook.com [213.199.154.10]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id s4K9VA4P016263 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 20 May 2014 11:31:13 +0200 Received: from [192.156.217.104] (86.188.197.189) by AM3PR05MB353.eurprd05.prod.outlook.com (10.242.247.21) with Microsoft SMTP Server (TLS) id 15.0.949.11; Tue, 20 May 2014 09:31:09 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 References: <537B0705.60605@morningstar2.co.uk> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [86.188.197.189] X-ClientProxiedBy: DB4PR02CA0018.eurprd02.prod.outlook.com (10.242.174.146) To AM3PR05MB353.eurprd05.prod.outlook.com (10.242.247.21) X-Forefront-PRVS: 02176E2458 X-Forefront-Antispam-Report: SFV:NSPM;SFS:(6049001)(6009001)(428001)(51704005)(51444003)(199002)(189002)(479174003)(24454002)(74482001)(83072002)(64126003)(81342001)(81542001)(87976001)(92726001)(85852003)(21056001)(83322001)(92566001)(221733001)(31966008)(74502001)(4396001)(42186004)(74662001)(101416001)(76176999)(65816999)(87266999)(54356999)(74826001)(83506001)(50466002)(79102001)(50986999)(102836001)(65806001)(65956001)(80022001)(99396002)(20776003)(47776003)(64706001)(36756003)(76482001)(561944003)(33656001)(66066001)(23676002)(80316001)(59896001)(46102001)(77982001);DIR:OUT;SFP:;SCL:1;SRVR:AM3PR05MB353;H:[192.156.217.104];FPR:;MLV:sfv;PTR:InfoNoRecords;A:1;MX:1;LANG:en; Received-SPF: None (: nag.co.uk does not designate permitted sender hosts) X-OriginatorOrg: nag.co.uk Message-ID: <537B20DA.3000002@nag.co.uk> Date: Tue, 20 May 2014 10:31:06 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: David Carlisle Subject: Re: Unicode math To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <537B0705.60605@morningstar2.co.uk> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: Envelope-To: X-GMX-Antispam: 0 (Mail was not recognized as spam); Detail=V3; X-GMX-Antivirus: 0 (no virus found) X-UI-Filterresults: notjunk:1;V01:K0:U3n2WyTwogg=:EMlXUY9kgRexuFVUT1SW2berWz VOJhm14H5BYRih72OV+9qGirVnjyh63dcGc359bqoU7yOxMNOW7cItN1Kpf6YNf8Un6GDrg3f ocpTTHLvFy7+OTLRlK1htipcqJtBMYjaDT/WVCRzB6lrE/1gsugsrHA15MgoQXyLAygWcxEjL UmxmQ/kDMpWk3K4rXgk4Dj7vVCCavfrqJx1QnZsacRSgN7Jc6YfHW0gilJAu/e1otkOUA8x+x YKt3nuuEbKlwxs9/2R2WP2phpbQPcpVCz8v7FbQ+jf8ZeDbOvOblpgcoloCb7ZtzipO6CFa+w ySBNygwgLLK1hKq7ft1gW5BKa/8b4t5PRB5ZwihaScgjCFheUAnA3ZoUZj7mIfrs3ucIEtrqx c+GHwEjsSBHMPWgJ8F5x6A5O/tCGqb1/MGLpCP1ZNeWtTvj7p4/IXYscMjlpz9ma5f4DdS0Te zuhqRrNDmySgMZTj6meqw9VKDIQBt5F8VU/kzq3A9WNNQLQoQD7+tlGKol8n7yRbemgYt4ukL Ghd06lspAOyCa1Q2t86VYGBjKEwwXtaSWWA1E0fhaHRD0UTXBEP5vFbveqCj0iH4ExDkGbCEl +76H1jcVSi1UauR5AQ72OSl2VGyzm13PIDLWwvhtxTbcO8ZST/yINpNGiySfPH5QdaKyl9xhH l+El29xoBM5keouuJ75BjTrJZCTZTPqJu+O5wRxKOzfb6MwDSqqsqA607BuRoe8IRL/xH2Y3K b23m5W45EvAI8JxfyWQYfpRF+KZT1M62VZKp8tuHcWXC9BL8qDJ0uBPV6L03SziR1nDEgWueh REcI7E7XaeZUBCZ5jcHkylaFGewo2z1gwlFfCYWsDsTq/m/ySxSuVBEXEYO6ndw8RqHrE3mUA dpsf14gWzAmfC1q5RVXxEeaCeK7LBKb3hwRwcS/Sy51crOgkI+cj+Dqf7P/p9IMGkvmzX7m8Q G3WMwPXQ3ojnK/IfInV/w/lZUkrBN4K+aLsYm1wCd4fMvHQh8aQIiil5QQ1RA9uGi7NftdnHU KLhTnqhWe/UO5+rMvlYsHXJKcZmKcXraPhkGXRJJfX+NpPlSU4R2V/fwbKLRlO3mW/NzL6Qkp mp3sMZGIHbI20BBWPMvHSk/1pgroJ2rZiLcB24fkQHXSNbFaj00xmIpABO+b6eQm3zEUMCANC l7jGrEDLA3DQevefS9oftqMwGOp/WvvabUwJ0w0eSsbwGSQSAJfUSJqXwv8FULf+lWrYKjlDX syWnxQ1Egcc9yxrwwYLHP92Pey5qqt1smbuH9RLaiTCHivgdmH8QrtmDSTI/cQbtN7UjRlTkX aVI3arhJAaA5lVEijyKBLYDk7PwsBbiHYY8SwbEUdyK/nUi6GR1KvoUi7PUiKtBC1+IDWZLQA ghh3Zjv8H8Ah1yALjMcyDZtnKB9fBICzJBKge7IkP3EA2UAg3wlk2Swhj6y7KAhHQehGFNisS cSIHOf/8iFjmK5laD4qgbs8BOK0L9ykbRv9nHlCggQtGrZwTXU8TiUtaU/hZrsfjbmYckZ+nH xOVufqleNeu6+PpOEefcxRg1dFqoCbnYXeOylFYWd X-UI-Loop:V01:XA94WiUI9kU=:f010GcSWJuzduPB0jujlPWB0sOkL0InTF54Ip62nqJQ= Status: R X-Status: X-Keywords: X-UID: 7413 On 20/05/2014 08:40, Joseph Wright wrote: > Hello Will, > > A few questions from me. One 'up front': where does \mathrm fit in to > all of this? I think \mathrm is conceptually no different to \mathbf so whatever so whatever scheme is used should apply to both. > To be clear, the Unicode position is that e.g. bold-B for magnetic field > should not come from the 'bold' font but from the bold-symbols part of a > single maths font: correct? That being the case, have the Unicode people > considered at all multi-letter identifiers or has this simply been > missed at present? (Anyone on the list sufficiently well-informed about > this?) I think that it is a mistake to look at unicode this way. Despite the appearance of "Unicode fonts" It's a standard primarily of _input characters_ for _plain text_ So the fact that there may or may not be particular characters in the Unicode math alphabet block isn't really of direct concern any more than the fact that there isn't an ffi ligature means that we shouldn't typeset an ffi ligature. Unicode just doesn't tell you whether f f i should be typeset as one two or three glyphs, and it doesn't tell you what font to use for typesetting bold math. (The tables in the font, once you have chosen a font, say something, but that's a different matter). That said, there are fonts that have useful glyphs in those positions and so clearly there should be a latex interface to access those. >> 3. To get proper bold symbols, including Greek, we'll need a whole new set >> of commands. These will need sensible names of some sort. Below I've chosen >> \symbf, etc., which doesn't look too bad to me. > By 'proper' here I assume you mean 'with attached mathematical meaning'? > I think it's fair to say that the LaTeX standard \mathbf does produce > bold symbols, and in the common case of matching text and maths fonts > the symbols also look 'right'. > -- Yes it isn't clear to me that any document would ever want both \mathbf for multi-letter identifiers and \symbf for single symbols. If the fonts use a matching design probably you just need \mathbf, and if the fonts don't use a matching design I think it would be better for consistency if you'd just use \mathbf as well. However sometimes there isn't a matching bold font, but there is (for a limited character range) a set of bold glyphs in the base math font in the bold math alphabet range. For that use I'd think a variant declaration which would define \mathbf to flip the mathcodes into the U+1Dxxx block using the base font rather than define it as a swutch to new \fam (\mathgroup) and would be useful. This latter mechanism could probably be a default for things like blackboard bold and calligraphic where you can't find default fonts by looking at the text font settings. But defining \symcal first as a name that always means the unicode block and then having top level options that do \let\mathcal\symcal rather than defining \mathcal directly would also work (and be more flexible in that it gives top level access to both if both are available people really need that. So I'm happy to run with Will's proposal to see where it leads.... David