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 s4LBNKXl001725 for ; Wed, 21 May 2014 13:23:21 +0200 Received: from relay.uni-heidelberg.de ([129.206.100.212]) by mx-ha.gmx.net (mxgmx111) with ESMTPS (Nemesis) id 0MW80b-1WGSnj0ETx-00XOaz for ; Wed, 21 May 2014 13:23:14 +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 s4LBJwxQ006890 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 May 2014 13:19:58 +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 s4L9TgRr005914; Wed, 21 May 2014 13:19:57 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 11053801 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 21 May 2014 13:19:57 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id s4LBJvpD001217 for ; Wed, 21 May 2014 13:19:57 +0200 Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lp0016.outbound.protection.outlook.com [213.199.154.16]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id s4LBJkkY006768 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Wed, 21 May 2014 13:19:49 +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; Wed, 21 May 2014 11:05:36 +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: Content-Type: multipart/alternative; boundary="------------080907010609040404050100" X-Originating-IP: [86.188.197.189] X-ClientProxiedBy: DB4PR02CA0014.eurprd02.prod.outlook.com (10.242.174.142) To AM3PR05MB353.eurprd05.prod.outlook.com (10.242.247.21) X-Forefront-PRVS: 0218A015FA X-Forefront-Antispam-Report: SFV:NSPM;SFS:(6049001)(428001)(199002)(189002)(479174003)(377454003)(24454002)(51704005)(79102001)(76176999)(87266999)(74826001)(101416001)(92726001)(80316001)(4396001)(19580405001)(19580395003)(83322001)(84326002)(221733001)(42186004)(21056001)(54356999)(65816999)(74482001)(102836001)(74502001)(99396002)(87976001)(33656002)(50986999)(46102001)(36756003)(81542001)(20776003)(71186001)(64706001)(81342001)(74662001)(77982001)(76482001)(59896001)(512944002)(85852003)(64126003)(80022001)(65956001)(66066001)(83506001)(83072002)(3076001);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: <537C887C.1000009@nag.co.uk> Date: Wed, 21 May 2014 12:05:32 +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: 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:tvyJYXtE9M4=:JzEJlT4g0+dsuRwSQN7sj9YYkP 1lOGC2Ay/Zav5tqo1L5Q13khjg2TS9Qge+W07CxV2nFo46iDxOK26+saetJ+L6sk7MA7R6Pz/ Erj7Kt37E9fH4+VaIV23FjYILDqenDd9nWz5xQJXhJHxsujsddiEQrNA+pCvC+khe5lAh+u1I GN1LGRc8FiyvRG8PEalm3O1TfTN39kfCiHjFCA234eg/8cXBBi8Zn/MoODkllKqmGxeSenFoU ctIpGlYmQATJwS93wZL9QuRlta3O/N+fDVadoPI11/ucxEed33s6LiS9zd/gIAzI9N17QSASN Pe03XqI34l2IQ6wyh/m4AHpWIj6HCtxXXr1/p1bISdhzldM+VohwPFNRPORAwSRk8QHSSGCbc L6tVJ3WKlk8zLqP0V1HlL1efmYAfbF02V++V88XqTxQ54RVDnJTTq5BV6xiOCi59njTwt/+Bl US+jh/CyErB0dsuMtPMSvKLwRtA/fMsYH5l1oqxBN5ZZTGvd29f8iNy1uznbi3jJpxWQ1+xg0 SMGplposEADPzgFm/bBRilM6sgP5XQz8jmzFy1NHbCJ4w4Jnl/2xs65KQsnwcJsdWn67fG7O+ 6l887MFSt83kywMRGDPvD9ztyYPAVyYmal1R9PxQh1lCTzOEj49tAieylv/YrrVZNhn1l6g/S 13uUKYyLqO3g4UMhTFO0pw/ItuSHl7dyA32s+2GSvhlJRCfe4J/iZPLgR3LOGl+Y/3nUVKOx6 xDFetVOVg/L34NuJ+KPpNkFdS+lP6TJQwg6/RruZY0JxN6jzHObSI66dIroMWnjAvF6phAdsI qzzvWZm3S/G/MHof8Nxe87G1ZYFqT5OKMuTR3bh1PcJFXKKLYUgBaEB5wo+KKFco+pTB3UNEq d2By5c+I3KB6R9val7l/47t5DsMpWpVN3OxopNIqkzOvamn1IBqpu4FkIxXppj2zoWK5/EUD4 nj763Jk9wiASduPWmERaP/UzvrbSq2yXAeAEWRo26p5d+TNDXivaWMsK15Jn3ktDPk2M1pqyZ yefKzQHhpvEc9aTnyXOh+QEwMVijJgxXJiKjnXnsZHBJhsqidpBxIi+1UjC9zpngyPOII0KNw yXkkJeE7fZaUiV044+eq4Dtnor6S9qj+6yM0uotIRKzPsGkeIOO3ogj7fxmbsXFUHxobxjbcM oYB1Acztol5c0xitUlPmDxYx21v1jVE/x/iFDHnK0waH2lfCtxPr4Bnhx6dkFHZXj5BwEz3SS VMELmizWlIU5w7S0zKvVlsfwNf6HXPzsSGEv0ultOVaDhT4gQlRC7C6+jnVkXdzeId9dzCT8I c6l2kTvesLzm9FbMMBlLu/2KnFIda8VzYAMOTdn76u8GkpzmgkmMdyGjyMeaFYX0LTnuWxJBD 0GjjOXYpBiSSh/wFjp3x/w6KVehQ1YH2EILQPT2+HJmRwQEHJvmLgI3GLuD2pxO+L2yvtdqnc DDfnwf1K64yjLhcqhsqcCh4PSQ9hbCkLKbHzwmJkNlv4E75BmNz6a7fwPO8xKO98qejC+buOH ZpUcBiq9ZbcaelR9D5fiw9foRfmkzNYbcYI2eySG5 X-UI-Loop:V01:lTo9tBtONKc=:VqKJJTLeBai1/8J5Dz4JT6o26xdu5pRHABIOJm7i0qg= Status: R X-Status: X-Keywords: X-UID: 7431 --------------080907010609040404050100 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by relay.uni-heidelberg.de id s4LBJwxQ006890 On 21/05/2014 11:49, Will Robertson wrote: > Hi Ulrike et al, > > > On 20 May 2014, at 11:34 pm, Ulrike Fischer wrote: > >> So in my opinion the current \mathbf-etc setup in unicode-math >> actually did the right thing and improved the standard >> \math-commands. > I=92m replying out of order, but I=92m still inclined to agree with you= here :) > The big problem was not handling \mathit properly. or at least the problem is more apparent for italic as the differences=20 between math and text setting are more glaring in that case:-) > > >> I wouldn't like to loose this completly. If \mathbf >> pointed to a textfont then everyone who wants the real math symbols >> would have to replace \mathbf in their code by \symbf. And back >> again if he wants to use a text font. >> >> Wouldn't it be possible to have a "\usetextfontasmathbf..." command >> which disables the mapping to the math plane? So that one doesn't >> have to switch between \symbf and \mathbf depending on the font >> setup of a document? > It has been possible for a long time to select a text font for a math a= lphabet in unicode-math, but this feature was probably not documented ver= y well. > If you try to select a particular unicode range such as \mathbfup and a= font simply doesn=92t have it (well, it only checks =93A=94 I think), th= e remapping doesn=92t occur and you get the ascii-range glyphs: Yes, although I think what's needed is an explicit way to do this rather=20 than relying on heuristics for example while answering a tex.sx question I wanted to use rsfs (or=20 euler) for script in addition or instead of the script in stix because well just because that's what the question=20 asked for, and it seemed that the easiest way currently is to use|\||mathup{\euler{A B C| to disable the mathcode=20 mapping which works but looks a bit odd. David --------------080907010609040404050100 Content-Type: text/html; charset="windows-1252" Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by relay.uni-heidelberg.de id s4LBJwxQ006890
On 21/05/2014 11:49, Will Robertson wrote:
Hi Ulrike et al,


On 20 May 2014, at 11:34 pm, Ulrike Fischer <news3@NILILAND.DE> wro=
te:

So in my opinion the current \mathbf-etc setup in =
unicode-math
actually did the right thing and improved the standard
\math-commands.
I=92m replying out of order, but I=92m still inclined to agree with you h=
ere :)
The big problem was not handling \mathit properly.

or at least the problem is more apparent for italic as the differences between
math and text setting are more glaring in that case:-)




I wouldn't like to loose this completly. If \mathb=
f
pointed to a textfont then everyone who wants the real math symbols
would have to replace \mathbf in their code by \symbf. And back
again if he wants to use a text font.=20

Wouldn't it be possible to have a "\usetextfontasmathbf..." command
which disables the mapping to the math plane? So that one doesn't
have to switch between \symbf and \mathbf depending on the font
setup of a document?
It has been possible for a long time to select a text font for a math alp=
habet in unicode-math, but this feature was probably not documented very =
well.
If you try to select a particular unicode range such as \mathbfup and a f=
ont simply doesn=92t have it (well, it only checks =93A=94 I think), the =
remapping doesn=92t occur and you get the ascii-range glyphs:

Yes, although I think what's needed is an explicit way to do this rather than relying on heuristics
for example while answering a tex.sx question I wanted to use rsfs (or euler) for script in addition or instead of
the script in stix because well just because that's what the question asked for, and it seemed=A0 that the easiest way
currently is to use \mathup{\euler{A B C to disable the mathcode mapping which works but looks a bit odd.



David

--------------080907010609040404050100--