- ntg-context - NTG Mailing Lists

Minor issue with font kern amount being doubled
by Joseph 31 Dec '20

31 Dec '20

1 0

lmtx: new text & math font stuff
by Hans Hagen 30 Dec '20

30 Dec '20

Hi, As you know, lmtx is also a place for experiments. Currently I'm playing a bit with fonts. Recently (as mentioned a whil eback) I added glyph scaling which permits interesting trickery, although one needs to be aware of how it combines with other features. Here's an example: \def\UnKernedTeX {T% {\glyph xoffset -.2ex yoffset -.4ex `E}% {\glyph xoffset -.4ex options "C0 `X}} \dorecurse{100}{ x \UnKernedTeX} There are alse \glyphxscale cum suis but again, beware that it might influence things when not used grouped. At some point this will be an option in scaled fonts (think of \tfc and such). It saves instances. You can get an idea with: \enableexperiments[text.fonts.compact] The 'text' in this command suggests that we can also do that with math and indeed we have \enableexperiments[math.fonts.compact] These directives have to come *before* loading fonts in order to be effective. Especially the math can bring down the number of font instances: text, script and scriptscript all use the same instance, which is good news. The bad news is that it's up to users to check how this plays out. There are some differences due to the fact that scaling happens elsewhere and otherwise which results in tiny differences (4/5th decimal). As said, these are experiments so ity might progress. I post intermediate versions because that way I can control it better. There is another variant in the planning. Yet another expriment (undecided if that will stay, i played with if before and then rejected it): \enabledirectives[fonts.injections.method=advance] If it stays I probbably have to patch some other code to better suit it. Overall, although in math it add to the overhead, due to the fact that math is hardly demanding (makes only a fraction of the rendering) the memory footprint can be quite a bit lower and performance a bit better (not that much). The measures used in rendering are kind of floating (recalculated often) when these mechanisms are enabled but my impression is that todays compilers make that hardly noticeable. As usual, it opens up possibilities, but of course at the price of testing. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

2 2

Protruding quotation marks obviate narrowed quotations
by Michael Guravage 30 Dec '20

30 Dec '20

Several months ago I posed the following question. When I start a paragraph with a \quote or a \quotation the left quotemark does not protrude, but when I use Unicode quotes it does. I would prefer to use the commands. Any suggestions on how I can achieve proper left protrusion without resorting to Unicode characters? Wolfgang suggested the following lines of code; which worked perfically. \setupquotation [method=font] \setupquote [method=font] Returning to this project after several months I observe that when I use a \start- stopquotation environment, the quotation is not narrowed. The \setupquotation command obviously affects both the \quotation command and \start- stopquotation environment. Is there an elegant way to apply the \setupquotation command and retain the quotation indentation? Cheers, Michael Here's a mwe. \showframe \showgrid \setupwhitespace[medium] % Setup hanging punctuation, less severe style \definefontfeature [default] [default] [protrusion=punctuation,expansion=quality] \setupalign[hz,hanging] % Provide protrusion for quotations. \setupquotation[method=font] % Toggle this line to see the effect. \setupquote[method=font] \starttext \startparagraph \quotation[method=font]{Love makes the world go round,} as an old proverb has it\ldots \stopparagraph \startquotation \input tufte \stopquotation \stoptext

1 0

Title in enumeration not working?
by Mikael Sundqvist 30 Dec '20

30 Dec '20

Hi, Has anything changed with titles and enumerations? I expected a title "Title" with the following setup. \defineenumeration[example][ text=Example, title=yes, ] \starttext \startexample[title={Title}] This is a test. \stopexample \stoptext But it does not show up. /Mikael

2 4

text alignment issue
by Alan Bowen 30 Dec '20

30 Dec '20

In the last few versions of luametatex standalone, paragraphs that were once justified now appear ragged right. My insertions of \setupparagraphs[align=wide/normal/yes] and \setupalign[wide/normal/yes] have had no effect. Is there some new coding that is needed to get justified text? Alan

1 1

Re: [NTG-context] adding url as a footnote in the caption of figure
by Jeong Dal 30 Dec '20

30 Dec '20

Dear Pablo, Thank you for your reply. I just search wiki not the mailing list. I never used \setupnote before. > I would say that LMTX is causing an issue here (but for sure Hans knows > better). > > The issue with your MWE is solved by adding: > > \setupnote[footnote][width=\textwidth] It works fine. Thanks again. Best regards, Dalyoung

1 0

adding url as a footnote in the caption of figure
by Jeong Dal 29 Dec '20

29 Dec '20

Hi, I am trying to add a url as a footnote in the caption. There is no error, but it is written in two lines in the footnote. I also try \hyphenatedurl, \letterslash in the wiki, but it is no use. I am using "ConTeXt ver: 2020.12.22 22:14 LMTX”. Thank you for reading. Best regards, Dalyoung Here is a MWE. \useMPlibrary[dum] \unexpanded\def\myurl#1{% \bgroup{\hyphenatedurl{#1}}\egroup} \starttext \startplacefigure[] {\startcombination[2*1] {\externalfigure[dummyz][width=.35\makeupwidth]}{Pegasus\footnote{\myurl{https://www.mcescher.com/gallery\letterslash recognition-success/no-105-pegasus/}}} {\externalfigure[dummy][width=.35\makeupwidth]}{Birds\footnote{\myurl{https://www.mcescher.com/gallery/recognition-success/no-128-bird/}}} \stopcombination} \stopplacefigure \stoptext

2 1

Best practices for multi-part book
by Denis Maier 29 Dec '20

29 Dec '20

Hi, I need to typeset a book that, due to space constraints, is going to be published in two volumes. Both volumes together will contain about 1500 pages, both volumes should be continuously paginated, i.e. if volume 1 ends at page 700 volume 2 will start at 801 (After the frontmatter maybe.) Both volumes will have the same frontmatter, maybe a different subtitle. Oh, and of course, both volumes shall have a complete table of contents. How would you approach such a task. I'm inclined to just treat the the whole thing as a single book, and split the the PDF at some point. Or, are there better ways that I could consider? Best, Denis

1 0

About xdecimal
by Jairo A. del Rio 28 Dec '20

28 Dec '20

Hi, list. I've tried using the xdecimal library included with LuaMetaTeX and I have some remarks: 1. Shifts are decimal, not binary: 145 >> 1 gives 14. 2. Integer division (//) is not implemented. Is that by design? 3. Following 2, what would be the way to handle integer division, remainder... for large numbers? Thank you in advance. Best regards, Jairo

2 3

Diagnositics in LuaTeX
by Henri Menke 28 Dec '20

28 Dec '20

Dear lists, Recently I've been working a bit on PGF/TikZ and many times I wished I had certain metrics that are available in regular programming languages. In particular I am missing: - A callback that is triggered when a macro is defined. This would allow me to trap when a cs is defined in the wrong place. That could probably be done by overriding `\def` but there are some gotchas with prefixes, e.g. `\long\def`. - A callback that is triggered when a token is expanded (or executed in the case of primitives). In conjunction with the previous request, this would allow me to measure code coverage by comparing which macros are defined and which ones are used. - Switches to trap on certain pathological events. For example I want to trap when TeX inserts a frozen \relax because a number couldn't be read. Another thing I want to trap is `Missing character: There is no <char> in font <font>!`. There are probably more silent TeX errors that I currently don't have in mind. Are these things possible in LuaTeX right now or could they be made possible in the future? Kind regards, Henri

2 1