August 2023 - ntg-context - NTG Mailing Lists

Fallbacks for design sizes in the current typescripts regime
by Hamid,Idris 23 Aug '23

23 Aug '23

Dear gang, Design sizes for typefaces -- aka "optical sizes" -- are no longer directly implemented in typescripts. From the manual Fonts out of ConTeXt by Hans Hagen, p. 109: "at some point the decision was made to kick out these definitions and move the burden of figuring out the right size to Lua." (Thus some large typescript collections painstakingly built over the years are now obsolete and have to be rewritten. Oh well..) But there is an issue in the new regime: In the old system, every typescript mapping to a font within a design-size range could have its own fallback. For example: % Small ="small point size" % Regular = "regular point size" % Bigger = "bigger point size" % Biggest = "biggest point size" \definefontsynonym [MyRomanRegular] [file:MyFont-Regular.ttf] [features=<features>,fallbacks=<fallback1>] \definefontsynonym [MyRomanSmall] [file:MyFont-Small.ttf] [features=<features>,fallbacks=<fallback2>] \definefontsynonym [MyRomanBigger] [file:MyFont-Bigger.ttf] [features=<features>,fallbacks=<fallback3>] \definefontsynonym [MyRomanBiggest] [file:MyFont-Biggest.ttf] [features=<features>,fallbacks=<fallback4>] In the new typescripts regime we keep one font from the design-size range in the typescript file; the rest of the optical sizes go into an lfg goodies file: \definefontsynonym [MyRomanRegular] \loadfontgoodies[myfonts-opticalsizes] % other three fonts go into an lfg table [file:MyFont-Regular.ttf] [features=<features>,fallbacks=<fallback1>] designsizes = { ["MyRomanRegular"] = { ["7pt"] = "file:MyFont-Small", ["8pt"] = "file:MyFont-Small", ["9pt"] = "file:MyFont-Regular", ["10pt"] = "file:MyFont-Regular", ["11pt"] = "file:MyFont-Regular", ["12pt"] = "file:MyFont-Bigger", ["14pt"] = "file:MyFont-Bigger", ["17pt"] = "file:MyFont-Biggest", ["21pt"] = "file:MyFont-Biggest", default = "file:MyFont-Regular", }, But there is an apparent drawback to this new way of doing things: It appears that only the default font can have an explicit fallback, and there appears that there is no straightforward way to map each of the other design sizes to its own fallback. If there is indeed no way to map each non-default design size to a fallback, then that constitutes a significant/unfortunate loss of functionality in the user interface. If this appearance of a loss reflects the reality of the situation, would like to kindly request that the original functionality be restored to the higher-level user interface, presumably within the lfg file. So perhaps something like a keyval fallbacks = { ["MyRomanRegular"] = { "file:MyFont-Small" = "fallbacks=<fallback2>", "file:MyFont-Regular", = "fallbacks=<fallback1>", "file:MyFont-Bigger", = "fallbacks=<fallback3>", "file:MyFont-Biggest", = "fallbacks=<fallback4>", }, On the other hand, if access to the former functionality is still there somewhere in the user interface, would like to humbly request that someone share where it is and how to use it! Thank you kindly for consideration of this request. Best wishes Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523

5 8

An strange error with section and page
by Xavier B. 23 Aug '23

23 Aug '23

Hi, I have a long document [https://repo.or.cz/apunts-espa-matematiques.git/blob/HEAD:/ng-exercicis.con…] which I migrated from MKIV to LMTX version of ConTeXt. As Wolfgang recommened. I migrated old syntax to new one and replace \page[yes] before each section to \setupheads[section][style={\bf \ssc}, alternative=margin, page=yes] but now after each section there is a new page. Why? I don't know. Can someone help me to see what happens? The source code is here [https://repo.or.cz/apunts-espa-matematiques.git] Thanks in advance, Xavier PS: Please CCme

2 2

MAPS nr 53
by luigi scarso 23 Aug '23

23 Aug '23

An unmissable issue of MAPS, totally dedicated to MetaPost by Taco. Once free I will put it in the mp repository. -- luigi

5 4

Better option for a macro with lots of arguments
by Andres Conrado Montoya 23 Aug '23

23 Aug '23

I have been using the following macro to add a bunch of sections to the start of chapters in a book, it works but I think is kind of weak: %%%%%%%%%%%%%%%%%%% \define[7]\metadatos{ \startsection[title={Resumen}] #1 \stopsection \startsection[title={Palabras clave}] #2 \stopsection \start \language[en] \startsection[title={Abstract}] #3 \stopsection \startsection[title={Keywords}] #4 \stopsection \stop \startsection[title={¿Cómo citar este capítulo? / How to cite this book?}] \startsubsection[title={Apa}] #5 \stopsubsection \startsubsection[title={Chicago}] #6 \stopsubsection \startsubsection[title={MLA}] #7 \stopsubsection \stopsection } \starttext % Then I call the macro like this: \metadatos{spanish abstract \input knuth}{some, comma, separated, keywords, in, spanish}{english abstract \input knuth}{same, comma, separated, keywords, in, english}{Apa citation style for this article}{Chicago citation style for this article}{MLA citation style for this article} \stoptext %%%%%%%%%%%%%%%%%%% I've been exploring different ways to do it better, but with not much luck, I was thinking something based in key=value assignments? setups? datasets? Not really sure, but If you know a better solution or point me in the direction of something I can use to replace that macro, it would be greatly appreciated. -- Andrés Conrado Montoya Andi Kú andresconrado(a)gmail.com http://sesentaycuatro.com http://messier87.com http://chiquitico.org ---------------------------------------- Los fines no justifican los medios, porque la medida verdadera de nuestro carácter está dada por los medios que estamos dispuestos a utilizar, no por los fines que proclamamos. ---------------------------------------- “You develop an instant global consciousness, a people orientation, an intense dissatisfaction with the state of the world, and a compulsion to do something about it. From out there on the moon, international politics look so petty. You want to grab a politician by the scruff of the neck and drag him a quarter of a million miles out and say, ‘Look at that, you son of a bitch.’” — Apollo 14 astronaut Edgar Mitchell

2 1

Cron <context@cgl> /var/www/aanhet.net/context/bin/cron/context-mirror
by root＠ntg.nl 23 Aug '23

23 Aug '23

rsync: [Receiver] failed to connect to rsync.pragma-ade.nl (213.125.29.165): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.2.7]

1 0

Cron <context@cgl> /var/www/aanhet.net/context/bin/cron/context-mirror
by root＠ntg.nl 23 Aug '23

23 Aug '23

rsync: [Receiver] failed to connect to rsync.pragma-ade.nl (213.125.29.165): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.2.7]

1 0

Cron <context@cgl> /var/www/aanhet.net/context/bin/cron/context-mirror
by root＠ntg.nl 23 Aug '23

23 Aug '23

rsync: [Receiver] failed to connect to rsync.pragma-ade.nl (213.125.29.165): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.2.7]

1 0

Cron <context@cgl> /var/www/aanhet.net/context/bin/cron/context-mirror
by root＠ntg.nl 23 Aug '23

23 Aug '23

rsync: [Receiver] failed to connect to rsync.pragma-ade.nl (213.125.29.165): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.2.7]

1 0

ConTeXt meeting 2023 attendance (please read)
by Taco Hoekwater 22 Aug '23

22 Aug '23

Hi all, This is a reminder that the registration for the upcoming ConTeXt meeting in Sibrina, Czech Republic is still open. The meeting will take place from Sept 10 to Sept 16. You can go to https://meeting.contextgarden.net for more information. You will also find the registration form there. You can (of course) attend in person, but registration for online only attendance is also possible! We hope to see you next month! NOTE: There have recently been problems with the delivery of the filled-in registration form to the organisers. If you have registered sometime *in the last month* but have not heard from Jano or me yet, please re-register (the form emailer is fixed) or at least drop us a message! Best wishes, Taco

1 0

your opinion about list structures
by Henning Hraban Ramm 22 Aug '23

22 Aug '23

Hi, this is about my ConTeXt book again… [ToC] At the moment, my table of contents has chapters and sections and is 8 pages long. I would probably hardly use it. Maybe it would be better to show only chapters (29 content + 12 appendix = 2 pages) and include a list of sections after the chapter title (or not at all). [Registers] I split between command and topic index (9 pages each), because I find it annoying to have the commands between the topics. I also include the topics that are mentioned in titles in the index, because I hate it if I must look in two places. (Otherwise I wouldn’t think about omitting the sections from the ToC.) At the moment there‘s also an index of todo items, but that will disappear before print. [Glossary] There’s a short dictionary of technical terms in the appendix (8.5 p.). Each lemma is also included in the index. Should I add a list of abbreviations? (TDS, TEI, OCG, RAL, PDF, SVG…?) They’re in the index and explained where they matter – I don’t think the meaning of many abbreviations like file types is important. [Other lists] Should I include a list of colors, like the output of \showcolor[crayola]? (I think it would only bloat the book, and everyone can create the list themselves.) I have lists of supported languages (should get checked), fonts in the distribution and all math fonts, because these are not easily reproducible (AFAIK). So, what do you think, and how do you like to work with technical books? What kind of information (about ConTeXt or documents/printing in general) do you find hard to find? Hraban

3 3