- ntg-context - Mailing Lists

Concerning text backgrounds (and further tuning) in references
by Jairo A. del Rio 25 Oct '20

25 Oct '20

Hi, list! I've seen the following question in TeX.SE. My attempt of solving was: https://tex.stackexchange.com/questions/567655/change-background-color-of-h… \setupinteraction [state=start]\definetextbackground[MyUrl] [ location=text, background=color, backgroundcolor=yellow, frame=off, ]\def\myfootnote#1{\MyUrl{\high{#1}}} \setupfootnotes[textcommand=\myfootnote] \definepapersize[default][A8,portrait]\setuppapersize [default]\useURL[aurl] [https://wiki.contextgarden.net] [] [\MyUrl{ConTeXt Garden}]\starttext Testing links to same page\footnote{This should create links to same page} and an external link: \from[aurl].\stoptext When one tries to use `\setupinteraction[...style=\MyUrl...]` either it doesn't work or displays a background which doesn't break well across lines. Is there a workaround or another method? Maybe a feature request for a more customizable setup for references? I had the same problem some time ago and I guess some others too. Thank you in advance, Jairo :)

2 2

space between chapter and chapter number (in words)
by jbf 24 Oct '20

24 Oct '20

I wonder if someone could explain to me what controls (or how to control) the space between Chapter and chapter number in my TOC given the setup I have. At the moment I get ChapterOne instead of Chapter One, and I do not know what is causing that. Here is my set up (at least all the parts that I think are controlling the appearance of Chapter Number in the TOC). Am I missing something? I thought perhaps the third line in the ChapterListCommand below might be what controls this, so I did try adding \hskip 1em (or 2em etc.) in the \currentlistsymbol section of that line, but it did nothing to solve the problem: \define[3]\ChapterListCommand {\hbox\bgroup \hbox to 2.5cm{\currentlistsymbol\hss}% number + labeltext \vtop\bgroup \hsize\dimexpr\makeupwidth-2.5cm\relax \doifsomething{\rawstructurelistuservariable{year}} {{\structurelistuservariable{year}}\crlf}% \currentlistentrytitle % title \doifsomething{\rawstructurelistuservariable{author}} {\crlf{\structurelistuservariable{author}}}% \hfill\currentlistentrypagenumber % pagenumber \egroup \egroup} \setuplabeltext [en] [ chapter=\bf Chapter , ] \setuplist [chapter] [label=yes, alternative=command, command=\ChapterListCommand] Julian

2 1

Filler rules
by Willi Egger 22 Oct '20

22 Oct '20

Good afternoon! I am dealing with a book, which has a short black rule under the title of the chapters. I see, that the old rule mechanisms are no more available in LMTX and are replaced by fillers. Now with the following setup, I would expect a 50mm line placed centered. Hoewever this seems not to work in this way. What am I missing? kind regards Willi \definefiller [Titlerule] [alternative=rule, left=\hfil, right=\hfil, method=local, width=50mm, height=2pt, leftmargin=1pt, rightmargin=1pt, align=middle] \starttext \midaligned{Some text} \filler[Titlerule] \stoptext

2 4

lmts status
by Hans Hagen 22 Oct '20

22 Oct '20

Hi, There haven't been lmtx updates for while now but there is a reason for it. On my machine I have luametatex 2.08 (so we jump number) which is in terms of typesetting the 20201010 version. That version has some reorganized internals, most have to do with consistency in the token interface at the Lua end. Of course there are some new and improved things too but those will be revealed in articles or manuals or the development status documents (already on my machine but they need checking). However, around that date I also decided to play a bit with some pending features: extended macro definitions and frozen macros. The first has to do with extensions to the macro definition code. Some are already present for a while, others have been added. The challenge there is to make defining macros somewhat more convenient and at the same time get rid of often too confusing error messages when a user does something bad with arguments (those foo_bar_whatever kind of things which might look impressive but often is pretty ugly). Of course that only makes sense when we keep the current performance: only gain, no pain. But, it also means that we need to adapt quite some code in order to benefit from it and when I started doing that one quickly ends up in a chain reaction: from a dozen files to over 100 and fives times that amount pending. But it's actually kind of fun (also for users I think). And hopefully Wolfgang will find my many errors. In parallel I played with the other feature: some kind of protection against macro abuse. This is actually related to the above because when you want to see macros with readable names in error messages, you cannot protect them with underscores and other ugly tricks that at the same time make stuff unreadable and ugly. We have a chicken and egg issue there. Anyway, the reason for this mail is that I want to warn users that the next lmtx release will use several protection mechanisms. Checking will for now be off by default but one can bump the level of protection at runtime. Just to give you an idea: we have primitives that can get a heavy protection against overload. We also have macro package system commands and these can get a pretty hard protection too. Commands defined by users (using \define...) can be treated less strict. Of course we also have all kind of runtime (temporary) macros that we have to protect (freeze) but also be able to redefine when we want to (think of variables). Then we have properties that are not primitives but nevertheless need the same strong protection, think of predefined counters, dimensions etc. So, you can imagine that there is some work involved in getting all that up and running. A side effect of that is that occasionally I notice some undesired hack or something that needs attention. The good news is that this probably can be pulled off without a real hit on performance. However, one side effect is that when users enable this (off by default) mechanism the might run into messages (when only warnings are enables) or errors (when they go for the full package). Now, in order to get this working well (as intended) I'd like users who then run into issues to make small examples that we we add to the test suite (unless of course they decide to fix the style, simply because they figure that they did something wrong). You're warned. So, when the next lmtx hits the web, make sure that you keep the old tree because one never knows where I mess up. I don't know when I'll upload. After all Wolfgang and I need to come to the conclusion that it's the way to go. More later, Hans PS. When doing this one runs into quite interesting conceptual issues, even in a system like context that is rather structured. But this is also why the final solution needs somewhat more work that one thinks when one starts with it. A macro language like tex is quite different from some regular programming language (and making it look like one doesn't help). ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

1 0

inter-word spacing
by Jano Kula 22 Oct '20

22 Oct '20

Hello, trying to reproduce the hand-printed original as close as possible I'm using \setupcharacterkerning. I can match character kerning, but inter-word spaces are different. What is the right option, command or feature to change it for current font and/or in the font definition? I haven't found any. MWE % macros=mkiv \setupcharacterkerning[large][factor=0.1] \setcharacterkerning[large] \starttext \input knuth \stoptext Thank you, Jano

2 2

Re: [NTG-context] Introduction to ConTeXt Wiki pages
by Damien Thiriet 22 Oct '20

22 Oct '20

Hi Sciurus, This Introduction page is very nice. Great Job! I would just replace the "first ConTeXt document" section with a link pointing to First_Document, section Create a ConTeXt file, because newcomers are likely to begin with that page anyway. Maybe using the same example would make sense? It would be also worth to index it in the Basics index. These are technical stuff that may be discussed further on in the wiki mailing-list. wiki(a)contextgarden.net Best regards, Damien Thiriet On Thu, Oct 22, 2020 at 01:43:28AM +0200, ntg-context-request(a)ntg.nl wrote: > > Hi all, > > Just wanted to put the word out that I have posted two new pages to the > Wiki, both aimed at new users of ConTeXt: > > https://wiki.contextgarden.net/Introduction > https://wiki.contextgarden.net/Some_Basic_Commands > > The first is an introduction to the general principles of writing documents > in ConTeXt, and the second is just a list of commands that beginning users > might be likely to want to use to customize their documents. I expect that I > will be continuing to update the second page in particular, as I find other > such commands or am able to provide further information or links. > > I am myself a relatively new user of ConTeXt (I started using it this > summer, having used LaTeX for many years), so there is a whole lot that I > don't know about it. I have tried to test out everything on these pages, so > while the information there may not be complete, it should at least be > correct. > > I don't claim to be any kind of authority on ConTeXt. I'm enjoying learning > it (including the many things that I have learned from this mailing list!), > and since I have seen in many places (including at the bottom of each > mailing list email) encouragement to contribute to the Wiki, I have begun > doing so. I am continuing to try to learn about ConTeXt, and I have decided > that as I learn things and/or find things on the Wiki that could use > supplementing, I'll try to add what I can. The Introduction to ConTeXt that > I have posted reflects the understanding of ConTeXt that I have gained over > these recent months of using it, however good or bad that understanding may > be. > > I welcome all manner of feedback on these pages (and of course feel free to > edit or contribute to them, as appropriate). Right now neither page is > linked to from anywhere else in the Wiki, so users wouldn't find them except > possibly by accident while searching for something else. If people think > that these pages would be useful, then I'd be happy to let the Wiki > administrators decide where best to put them. > > Thanks, > > > Sciurus > > > > > ------------------------------ > > Subject: Digest Footer > > ___________________________________________________________________________________ > If your question is of interest to others as well, please add an entry to the Wiki! > > maillist : ntg-context(a)ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://tex.aanhet.net > archive : https://foundry.supelec.fr/projects/contextrev/ > wiki : http://contextgarden.net > ___________________________________________________________________________________ > > > ------------------------------ > > End of ntg-context Digest, Vol 196, Issue 44 > ********************************************

1 0

The correct way to add emphasis to text using italics
by Andres Conrado Montoya 22 Oct '20

22 Oct '20

I've seen in several articles on the Wiki, some differences about how this is done, and I'm confused about the differences: *Font_Switching* says: "There is a font switch \em to emphasize text. This is somewhat special: it does automatic italic correction and changes the alternative depending on the current alternative. For example, if the current font alternative is normal (i.e. upright), \em switches to slanted; and if the current font alternative is slanted, \em switches to normal." And using \definebodyfontenvironment[default][em=italic] to use italic instead of slanted; for OpenType fonts, recommends using \definefontfeature[default][default][itlc=yes] to also activate the italic correction. However, this seems not to work in x(ht)ml export. If you go to *Export*, it says: "Also note that switches like \em don’t translate into output structure, you need to \definehighlight[emph][style={\em}] and use as \emph{emphasized}." This is what I'm currently using. Other parts of the Wiki show a similar solution, but using style=italic, or style={\it}; I've seen others, but now I can't find them. Could you please guide me as to where is this documented in the manuals? Is there any particular reason to choose any of these approaches above the others? What is the recommended option if you want to have the \em properties for emphasized text, but works for BOTH pdf and x(h)tml export? Thank you for your time. -- 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

Introduction to ConTeXt Wiki pages
by type＠projectivespace.com 22 Oct '20

22 Oct '20

Hi all, Just wanted to put the word out that I have posted two new pages to the Wiki, both aimed at new users of ConTeXt: https://wiki.contextgarden.net/Introduction https://wiki.contextgarden.net/Some_Basic_Commands The first is an introduction to the general principles of writing documents in ConTeXt, and the second is just a list of commands that beginning users might be likely to want to use to customize their documents. I expect that I will be continuing to update the second page in particular, as I find other such commands or am able to provide further information or links. I am myself a relatively new user of ConTeXt (I started using it this summer, having used LaTeX for many years), so there is a whole lot that I don't know about it. I have tried to test out everything on these pages, so while the information there may not be complete, it should at least be correct. I don't claim to be any kind of authority on ConTeXt. I'm enjoying learning it (including the many things that I have learned from this mailing list!), and since I have seen in many places (including at the bottom of each mailing list email) encouragement to contribute to the Wiki, I have begun doing so. I am continuing to try to learn about ConTeXt, and I have decided that as I learn things and/or find things on the Wiki that could use supplementing, I'll try to add what I can. The Introduction to ConTeXt that I have posted reflects the understanding of ConTeXt that I have gained over these recent months of using it, however good or bad that understanding may be. I welcome all manner of feedback on these pages (and of course feel free to edit or contribute to them, as appropriate). Right now neither page is linked to from anywhere else in the Wiki, so users wouldn't find them except possibly by accident while searching for something else. If people think that these pages would be useful, then I'd be happy to let the Wiki administrators decide where best to put them. Thanks, Sciurus

1 0

oldstyle numerals in STIX Two Math
by Alan Bowen 21 Oct '20

21 Oct '20

I am trying to get the STIX Two fonts to display oldstyle numerals. I have the oldstyle numerals in STIX Two Text, the problem is the math font. So far, my mwe is: \definefontfamily[mainface][rm][STIX Two Text][] %onum=yes does not seem to work \definefontfamily[mainface][mm][STIX Two Math][] \definefontfeature[f:oldstyle][onum=yes] \setupbodyfont[mainface, 18pt] \addfeature{f:oldstyle} \starttext 123456789 \blank[big] $\sqrt{2} + 1234$ \stoptext Any pointers will be greatly appreciated. Alan

3 3

typos in sort-lan.lua
by Henning Hraban Ramm 19 Oct '20

19 Oct '20

I stumbled upon a few typos in the sort order definitions: In Hebrew and Yiddish, there are many unclosed brackets: definitions['he'] = { 979 entries = { 980 ['א'] = 'א', ['ב'] = 'ב', ['ג'] = 'ג', ['ד'] = 'ד', ['ה'] = 'ה', 981 ['ו'] = 'ו', ['ז'] = 'ז', ['ח'] = 'ח', ['ט'] = 'ט', ['י'] = 'י', 982 ['כ'] = 'כ', ['ל'] = 'ל', ['מ'] = 'מ', ['נ'] = 'נ', ['ס'] = 'ס', 983 ['ע'] = 'ע', ['פ'] = 'פ', ['צ'] = 'צ', ['ק'] = 'ק', ['ר'] = 'ר', 984 ['ש'] = 'ש', ['ת'] = 'ת', 985 }, etc. Hraban

1 0