From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/94499 Path: news.gmane.org!not-for-mail From: Thomas Fehige Newsgroups: gmane.comp.tex.context Subject: Re: uppercase, small caps, numerals and German capital sharp s Date: Wed, 20 Apr 2016 16:03:41 +0200 Message-ID: <57178C3D.4090008@fehige.de> References: <5715D9D5.5000403@fehige.de> <57161F10.3010901@gmail.com> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3946060888840505241==" X-Trace: ger.gmane.org 1461161072 20218 80.91.229.3 (20 Apr 2016 14:04:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 20 Apr 2016 14:04:32 +0000 (UTC) To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Wed Apr 20 16:04:11 2016 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1assjg-000304-OG for gctc-ntg-context-518@m.gmane.org; Wed, 20 Apr 2016 16:04:08 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id C9305ABD3; Wed, 20 Apr 2016 16:03:56 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v6Y1Oq9zblmv; Wed, 20 Apr 2016 16:03:56 +0200 (CEST) Original-Received: from zapf.ntg.nl (localhost [IPv6:::1]) by zapf.ntg.nl (Postfix) with ESMTP id 0F0C6ABD1; Wed, 20 Apr 2016 16:03:56 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id C9293ABD1 for ; Wed, 20 Apr 2016 16:03:54 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xmwuorIha3J2 for ; Wed, 20 Apr 2016 16:03:52 +0200 (CEST) Original-Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.134]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by zapf.ntg.nl (Postfix) with ESMTPS id C91B8ABD0 for ; Wed, 20 Apr 2016 16:03:42 +0200 (CEST) Original-Received: from [192.168.178.24] ([77.3.179.183]) by mrelayeu.kundenserver.de (mreue001) with ESMTPSA (Nemesis) id 0MOo4s-1amqa00886-006362 for ; Wed, 20 Apr 2016 16:03:42 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 In-Reply-To: <57161F10.3010901@gmail.com> X-Provags-ID: V03:K0:zdMco6YXEnuJ6f4VrLBaehIv4q7bU9FunG93Aggi9m3ozpJDPEP Vi4NTcOd8tUCV8zGoDP7Tuw+iVk6OQMSCZenaTmyj6crJ4vXLMhLD2wqE9qRr0TAKqfM+6p LrhJ2u4FSQeDMNL9Pi9ye4hxiYpEGf2qV9LA15ZDNPbk1oDMaZUg7iN3XBl4FrTAd3mIGFx hObMr6b6xQWPDDYtBladQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:pI1iIgA1RTw=:XksozsTPnUY2RNY7E+mAZS Rn9CexLpG3zdXnB9v3iUGb19hIhYzzI77TwW8XeV1603Y/lO+EOst+RUv5onHH2rsjGUlVrq3 9InbbzYbX7Z9dhiks+L3oB1fEv/mcHrJgdooVFWGzJd4Ax4BOjIvsoxrESd2FunsCbudrnXVn bREIzjvF5pzDDR1AzE/uuyqAwDUg5+aPI7ofZG/lGAB0fDM5oCO/MNiuVPSVcXVYoN+hkC7p8 +Zz3ok4cmxzkQre5DAhlTnJmPJkF+zaVm0XxWHWTTSpRl0ojJvnRZrZQHgI0pX62Q2/55LSMa UTOqPpbhx/Pnjl2rUcJRXsTGwpttDCiu5JS4lSLcMw9s0/JJ9/ECF+gx+n05aYeLE5bUe/qfa 1yGk2fzCuXOCFIqe/QKaW3vDP+MzrZqWMaUuvkTeOzIndgO+5nVwN3JpoOdyg8TaxVZmqNT+G wxw8uRjMAk09gn9/M3qkwnHeccUUxCtaEYxVzBMByqaVQTKrJhBaWJ52g0RyPSXDenNuhoU6H vFIoBgRy0fqy5zMLBYxXGIv+9uzTL+AaPj5q0LU/IwotkD+Ygh+pOJkbIHQ3ePIycuBg/tOg9 r8wqrKU4M0lDQMmtsObF4oZ5xAyW81MkOCqSHeb1T592RTQUTuY1SxZWl9A7njAQmEEzdiP7Z OpKuL6iFF7VxIw4RdMtZQp46lpX2NnRXfvlYRCZAY3c2fPnwoyzPIyvyh9NlQSQwX8LgnPjC7 Wuom3ftoNi8vSY5x X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.16 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntg-context-bounces@ntg.nl Original-Sender: "ntg-context" Xref: news.gmane.org gmane.comp.tex.context:94499 Archived-At: This is a multi-part message in MIME format. --===============3946060888840505241== Content-Type: multipart/alternative; boundary="------------050103050600080203000807" This is a multi-part message in MIME format. --------------050103050600080203000807 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Wolfgang, > Use separate threads for each problem. The uppercase sharp s=20 > replacement with \WORD can be changed in the next beta. > > %% begin example are you saying, use this example as long as the new beta isn't out yet,=20 or are you saying, this example will work as soon as I'll use the new=20 beta? It doesn't seem to do anything right now, not even an error message= . I was looking for a general way how to substitute one glyph with another=20 depending on context, thus I can't see how there are different problems=20 in my post? But it's good to hear that others have thought at least of a=20 partial solution. Is my guess right that normally the author of a font ought to provide=20 otf features that can be switched on and off to get one result instead=20 of the other? That area seems to be utter chaos in the Calluna fonts. Cheers -- Thomas Am 19.04.2016 um 14:05 schrieb Wolfgang Schuster: >> Thomas Fehige >> 19. April 2016 um 09:10 >> Hello, >> >> I'm new to ConTeXt and this list. After a long time of using LaTeX=20 >> and xeLaTeX I was finally lured into trying ConTexT by its ability of=20 >> grid typesetting. >> >> Today's problem is a bit complex. In a book project I have several=20 >> points where stuff is capitalized or turned into caps+smallcaps or=20 >> pure smallcaps. My guess is that that should work either with=20 >> \WORD{Stuff}, \Cap{Stuff} and \cap{Stuff} or with \uppercase, \sc,=20 >> and {\sc\lowercase{Stuff}}. (Not quite, it seems) >> >> I'll use a commercial font called Calluna, but have added Linux=20 >> Biolinum O to the example for those who don't want to download=20 >> Calluna (the "Regular" can be "bought" for free, e.g. at=20 >> https://www.fontspring.com/fonts/exljbris/calluna). >> >> Both Calluna and Biolinum contain the glyph "LATIN CAPITAL LETTER=20 >> SHARP S" at "1E9E. Calluna also has a small caps version at "F727",=20 >> while Biolinum has it at "E092. I'd like to use these glyphs in the=20 >> capitalizations mentioned, but that only works erratically (cf.=20 >> example). >> >> Secondly, Calluna comes with oldstyle numerals switched on, which is=20 >> nice for normal text, but should change to proportional lining=20 >> numbers in uppercase and to small-cap proportional lining numbers in=20 >> an all-small-cap text. I'm not sure what I'd want in a caps+smallcaps=20 >> context, but certainly not oldstyle numerals with their descenders. > Use separate threads for each problem. The uppercase sharp s=20 > replacement with \WORD can be changed in the next beta. > > %% begin example > \usemodule[lingual-de] > > \setupbodyfont[libertine] > > \starttext > > Gru=C3=9F Stra=C3=9Fe Bu=C3=9Fe > > \WORD{Gru=C3=9F Stra=C3=9Fe Bu=C3=9Fe} > > \enabledirectives[fonts.uppercasesharps] > > \WORD{Gru=C3=9F Stra=C3=9Fe Bu=C3=9Fe} > > \disabledirectives[fonts.uppercasesharps] > > \WORD{Gru=C3=9F Stra=C3=9Fe Bu=C3=9Fe} > > \stoptext > %% end example > > Wolfgang > > > _______________________________________________________________________= ____________ > If your question is of interest to others as well, please add an entry = to the Wiki! > > maillist :ntg-context@ntg.nl /http://www.ntg.nl/mailman/listinfo/ntg-c= ontext > webpage :http://www.pragma-ade.nl /http://tex.aanhet.net > archive :http://foundry.supelec.fr/projects/contextrev/ > wiki :http://contextgarden.net > _______________________________________________________________________= ____________ --------------050103050600080203000807 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Wolfgang,
Use separate threads for each problem. The uppercase sharp s replacement with \WORD can be changed in the next beta.

%% begin example
are you saying, use this example as long as the new beta isn't out yet, or are you saying, this example will work as soon as I'll use the new beta? It doesn't seem to do anything right now, not even an error message.

I was looking for a general way how to substitute one glyph with another depending on context, thus I can't see how there are different problems in my post? But it's good to hear that others have thought at least of a partial solution.

Is my guess right that normally the author of a font ought to provide otf features that can be switched on and off to get one result instead of the other? That area seems to be utter chaos in the Calluna fonts.

Cheers -- Thomas

Am 19.04.2016 um 14:05 schrieb Wolfgan= g Schuster:
19. April 2016 um 09:10
Hello,

I'm new to ConTeXt and this list. After a long time of using LaTeX and xeLaTeX I was finally lured into trying ConTexT by its ability of grid typesetting.

Today's problem is a bit complex. In a book project I have several points where stuff is capitalized or turned into caps+smallcaps or pure smallcaps. My guess is that that should work either with \WORD{Stuff}, \Cap{Stuff} and \cap{Stuff} or with \uppercase, \sc, and {\sc\lowercase{Stuff}}. (Not quite, it seems)

I'll use a commercial font called Calluna, but have added Linux Biolinum O to the example for those who don't want to download Calluna (the "Regular" can be "bought" for free, e.g. at ht= tps://www.fontspring.com/fonts/exljbris/calluna).

Both Calluna and Biolinum contain the glyph "LATIN CAPITAL LETTER SHARP S" at "1E9E. Calluna also has a small caps version at "F727", while Biolinum has it at "E092. I'd like to use these glyphs in the capitalizations mentioned, but that only works erratically (cf. example).

Secondly, Calluna comes with oldstyle numerals switched on, which is nice for normal text, but should change to proportional lining numbers in uppercase and to small-cap proportional lining numbers in an all-small-cap text. I'm not sure what I'd want in a caps+smallcaps context, but certainly not oldstyle numerals with their descenders.
Use separate threads for each problem. The uppercase sharp s replacement with \WORD can be changed in the next beta.

%% begin example
\usemodule[lingual-de]

\setupbodyfont[libertine]

\starttext

Gru=C3=9F Stra=C3=9Fe Bu=C3=9Fe

\WORD{Gru=C3=9F Stra=C3=9Fe Bu=C3=9Fe}

\enabledirectives[fonts.uppercasesharps]

\WORD{Gru=C3=9F Stra=C3=9Fe Bu=C3=9Fe}

\disabledirectives[fonts.uppercasesharps]

\WORD{Gru=C3=9F Stra=C3=9Fe Bu=C3=9Fe}

\stoptext
%% end example

Wolfgang


____________________________________________________=
_______________________________
If your question is of interest to others as well, please add an entry to=
 the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/m=
ailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextre=
v/
wiki     : http://contextgarden.net
_________________________________________________________________________=
__________

--------------050103050600080203000807-- --===============3946060888840505241== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv IGh0dHA6Ly90ZXguYWFuaGV0Lm5ldAphcmNoaXZlICA6IGh0dHA6Ly9mb3VuZHJ5LnN1cGVsZWMu ZnIvcHJvamVjdHMvY29udGV4dHJldi8Kd2lraSAgICAgOiBodHRwOi8vY29udGV4dGdhcmRlbi5u ZXQKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX18= --===============3946060888840505241==--