ntg-context April 2020

ntg-context@ntg.nl

48 participants
108 discussions

Trouble setting PDF boxes
by Jack Steyn 30 Apr '20

30 Apr '20

Hi, I am having trouble setting the PDF boxes to my desired dimensions. Suppose I have \setuppapersize[*a*][*b*]. I want CropBox = MediaBox = *b*. So far, so good: I can just use cropoffset=0mm in \setuplayout. But I want TrimBox = *a*. However, as far as I can see, I can't achieve this using trimoffset in \setuplayout unless (width of *b*) – (width of *a*) = (height of *b*) – (height of *a*), which does not hold in my case. So it looks like I need to find another way to set the TrimBox (and the BleedBox, which I want to be 3mm wider and taller than the TrimBox). Does anyone know how to do this? Best, Jack

3 6

Fwd: Unicode normalization and Hebrew in ConTeXt
by Joey McCollum 30 Apr '20

30 Apr '20

Thank you for the prompt and thorough response! If the reorderings have to be done for each pair of characters in different combining classes that are not in the expected typographical order, then there will be a lot (probably hundreds) of substitution rules. I am not very familiar with coding in Lua, but if there is a way to add substitution features for specific classes of points, then that would require a lot fewer cases. Unicode's canonical ordering of Hebrew marks is based on their combining classes, with characters in higher combining classes being sorted after those with lower combining classes in canonical order. The typographically recommended ordering of certain characters is found in Table 1 (p. 12) of https://www.sbl-site.org/Fonts/SBLHebrewUserManual1.5x.pdf. The following list of character classes, with information about their Unicode combining classes (which I retrieved from the Lua script https://raw.githubusercontent.com/michal-h21/uninormalize/master/char-def-w…), is indexed after the character classes described in that table: 1. The consonants (Unicode points 05D0-05EA) have no combining class and are never reordered; this is typographically correct. 2. Shin dot and sin dot (05C1-05C2) should be next, but Unicode places them in combining classes 24 and 25, after the characters in recommended classes 3-5 and many of the characters in recommended class 6. 3. Dagesh / mapiq (05BC) should be next, but Unicode assigns it a combining class of 21. This means that it will be incorrectly ordered before characters in recommended class 2 and after characters in recommended classes 4-6 after Unicode normalization. 4. Rafe (05BF) should be next, but Unicode assigns it a combining class of 23. Thus, it will be correctly placed after characters in recommended class 3, but incorrectly placed before characters in recommended class 2 after Unicode normalization. 5. The holam and holam haser vowel points (05B9-05BA) should be next, but Unicode places them in combining class 19. This means that it will be placed incorrectly before characters in recommended classes 2-4 and after all characters in recommended class 6 except 05BB after Unicode normalization. 6. The characters in 0591, 0596, 059B, 05A2-05A7, 05AA, 05B0-05B8, 05BB, 05BD, 05C5, 05C7 should be treated as being in the same class, but Unicode places them in combining classes 10-18, 20, 22, and 220. 7. The prepositive marks yetiv and dehi (059A, 05AD) should be next; Unicode places them in combining class 222, so they should correctly come after all characters in recommended classes 1-6. 8. The characters 0307, 0593-0595, 0597-0598, 059C-05A1, 05A8, 05AB-05AC, 05AF, 05C4 should be treated as being in the same class; Unicode places them in combining class 230, so they should correctly come after all characters in recommended classes 1-7. 9. The postpositive marks segolta, pashta, telisha qetana, and zinor (0592, 0599, 05A9, 05AE) should be next; Unicode places them in combining class 230, so they will need to be reordered after the characters in recommended class 8. This a lot of information, and I've probably not presented it as clearly as I could, so if there is any confusion, please let me know, and I can try to explain better. If there is any other information you need, please let me know. Thanks again! On Tue, Apr 28, 2020 at 9:17 AM Hans Hagen <j.hagen(a)xs4all.nl> wrote: > On 4/28/2020 1:59 PM, Joey McCollum wrote: > > \definefontfeature[f:pointedhebrew][default][ > > ccmp=yes, > > mark=yes, > > script=hebr > > ] > > \definefontfamily[hebrew] [rm] [SBL Hebrew] [features=f:pointedhebrew] > > %Set the body font: > > \setupbodyfont[hebrew] > > %Set up right-to-left alignment: > > \setupalign[r2l] > > \starttext > > %Characters after normalization, in Unicode canonical order (bet + > > segol + dagesh + final nun): > > בֶּן > > > > %A word with characters in typographically recommended order (bet + > > dagesh + segol + final nun): > > בֶּן > > \stoptext > > \startluacode > fonts.handlers.otf.addfeature { > name = "normalizehebrew", > type = "chainsubstitution", > prepend = 1, > lookups = { > { > type = "multiple", > data = { > [0x5B6] = { 0x5BC, 0x5B6 }, > }, > }, > }, > data = { > rules = { > { > current = { { 0x5B6 }, { 0x5BC } }, > lookups = { 1, 0 }, > }, > }, > }, > } > \stopluacode > > \definefontfeature > [f:pointedhebrew] > [hebrew] > [normalizehebrew=yes] > > \definefontfamily[hebrew] [rm] [SBL Hebrew] [features=f:pointedhebrew] > > \setupbodyfont[hebrew] > > \setupalign[r2l] > > \starttext > בֶּן \quad בֶּן \par > \stoptext > > How many such reorderings are there? (I saw some document about that > font and it sounds like a bit messy wrt all these input variants.) > > (there are several mechanisms in context to deal with such issues, it's > all about getting specs from users i.e. tex is all about control so in > principle it should be doable) > > 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 > ----------------------------------------------------------------- >

3 4

Problem including svg files with Inkscape 1.0~rc1-4
by Romain Diss 30 Apr '20

30 Apr '20

Hi, The last release candidat of Inkscape (1.0~rc1-4 on my Debian sid) doesn't provide the `--export-pdf=` option anymore. So context can not convert svg files into the corresponding `m_k_i_v_*` pdf. It seems that the `--export-filename=` option does the job. Thank in advance. -- Romain Diss

3 7

Project setup query
by Alan Bowen 30 Apr '20

30 Apr '20

This is a minor issue—to which I expect the answer will be simple, something I should know by now but do not. I am just trying to see if I can streamline a working directory. In Directory01, I have a number of prd_NameXX.tex files as well as a Directory02 which contains .tex files that are to be called on by each one of the prd_Name.tex files. Is there a way to identify the TEX root for each of the common files (in Directory02) so that the file will be processed when I process any one of the prd files in Directory01? I have tried % !TEX root=../prd_\mystring.tex with, e.g., \def\mystring{Name01} in the prd_Name01.tex file, but that does not seem to work—the various .tex files re not found. What puzzles me is that the environment files in Directory02 are found. (That they are identified in a prj file in Directory01 does not seem to be the reason why.) There is no problem if I move the contents of Directory02 into Directory01. Alan

2 1

Getting page width and height in Lua
by Jack Steyn 30 Apr '20

30 Apr '20

If I want to get the paper width and height to use in some Lua code, I can use: local paperwidth, paperheight = backends.pdf.codeinjections.getpagedimensions() But what if I want to get the page width and height? That is, the width and height of the first argument in the two-argument version of \setuppapersize. Does anyone know how I can obtain these using Lua? Many thanks, Jack

2 1

Is this a MetaFun bug or intended behaviour?
by Gerben Wierda 30 Apr '20

30 Apr '20

I wanted to use the macro simplified to remove duplicate points from a path, but it removes more than that: metapost log > (127,-107)..controls (117,-107) and (107,-107) metapost log > ..(97,-107)..controls (97,-130.33333333333334) and (97,-153.66666666666666) metapost log > ..(97,-177)..controls (117,-177) and (137,-177) metapost log > ..(157,-177)..controls (157,-170.33333333333334) and (157,-163.66666666666666) metapost log > ..(157,-157) metapost log > metapost log > >> Path at line 0: metapost log > (97,-177)..controls (117,-177) and (137,-177) metapost log > ..(157,-177)..controls (157,-170.33333333333334) and (157,-163.66666666666666) metapost log > ..(157,-157) First is path, second is simplified path. Is simplified maybe only supposed to work with cycles? G

1 0

image across 2 page spread
by jbf 30 Apr '20

30 Apr '20

Hi list, With 99% of work complete on a book, including single page images, I now find myself confronted with a final problem: how to run one image across facing pages or in other words, one image (plus its caption) across a two-page spread, such that there is no gap. I have tried a number of fairly crass attempts (obviously too simple) to see if I could get somewhere near what I want, e.g. \externalfigure[plate12.jpg][width=\paperwidth, height=.7\paperheight, frame=none] {\tfx \sc Plates 12, 13. \tfx Twenty trucks from the Netherlands setting off} \externalfigure[plate13.jpg][width=\paperwidth, height=.7\paperheight, frame=none] {\tfx for their first mission amongst the German diaspora.} My thinking here was that \paperwidth might help extend the image to the inner edge on the left-hand page, but it doesn't work that way for the right-hand page, since there it extends to the outer edge, not the inner edge! The .7\paperheight was to provide room for the caption. But all in all, this is no solution! If it is any help, the setup dimensions for the book are US Digest: \definepapersize [ACN][width=5.5in,height=8.5in] % w140mm x h216mm I then looked up how one might do it in LaTeX, and found the following link: https://tex.stackexchange.com/questions/23860/how-to-include-a-picture-over… How much of that would be transferable to ConTeXt? (I am thinking particularly of the |\newcommand*{\twopagepicture}[4]| bit. There are explanations for how to do this in InDesign, and since it is something someone might often want to do (e.g. in magazines), I also thought it might be easier to find reference to it on Contextgarden, yet haven't found anything there. But I am sure ConTeXt has a way to do this. Could someone point me in the right direction with this please? Julian ||

4 3

further to the single image across two page spread
by jbf 29 Apr '20

29 Apr '20

After sending my previous email, I realised that my own attempt could be quite misleading, since there I was using two separate images across facing pages. I was simply trying to get the two images to 'marry' across the divide! But that is not my problem, since what I need to do is to get the one image (a suitable landscape image I might add) to run seamlessly across a two-page spread (which is what the LaTeX example I gave does). Sorry for any confusion, Julian

1 0

two additional pagenumber series
by Pablo Rodriguez 29 Apr '20

29 Apr '20

Dear list, for one of the documents I share with others, I need to add five pagenumber series. I’m already using realpage, userpage and subpage. I have just tried to use \definecounter, but it doesn’t work. \setuppapersize[A9] \definecounter[ncounter] [way=bychapter] \starttext \rawcountervalue[ncounter]\page \incrementcounter[ncounter][1] \page \lastcountervalue[ncounter] \chapter{} \lastcountervalue[ncounter] \stoptext I don’t know how to link any page increment to the defined counter. Although method is page, this seems to be related to a different issue. My question is: how could I get new pagenumber series using \definecounter? Many thanks for your help, Pablo -- http://www.ousia.tk

3 3

Right-to-left pagecolumns and markings in ConTeXt
by Joey McCollum 29 Apr '20

29 Apr '20

I am trying to typeset a two-column text in a right-to-left language using ConTeXt. Because I want footnotes in this text to be set ragged-bottom, I am using pagecolumns instead of standard columns. I also want to track the first and last textual division markers on each page using markings. Combining all of these ingredients seems to create a problem in ConTeXt: when the pagecolumns are set in right-to-left order, the top and bottom marks fetched are always the top and bottom marks in the left column, while the true top mark should be the top mark of the right column. I've observed this behavior using text in an actual right-to-left language, but the following minimal (non-)working example with an English sample text demonstrates the same behavior: ``` %Create a new markset to use: \definemarking[TestMark] %Setup header to reflect top and bottom marks: \setupheadertexts[top: {\fetchmark[TestMark][top]}][bottom: {\fetchmark[TestMark][bottom]}][top: {\fetchmark[TestMark][top]}][bottom: {\fetchmark[TestMark][bottom]}] %even left, even right, odd left, odd right %Setup the columns layout: \definepagecolumns [example] [ n=2, %number of columns direction=reverse, %does not work if ending comma is removed! ] \starttext \startpagecolumns[example] \marking[TestMark]{1}(1) \input knuth\par \marking[TestMark]{2}(2) \input knuth\par \marking[TestMark]{3}(3) \input knuth\par \marking[TestMark]{4}(4) \input knuth\par \marking[TestMark]{5}(5) \input knuth\par \marking[TestMark]{6}(6) \input knuth\par \marking[TestMark]{7}(7) \input knuth\par \marking[TestMark]{8}(8) \input knuth\par \stoppagecolumns \stoptext ``` I typeset this using ConTeXt version 2020.03.10, as released with TeXLive 2020. As my comment in the MWE points out, there also seems to be a bug in the key-value parsing of \definepagecolumns that causes it not to parse the direction=reverse input unless it is followed by a comma. Is there some way I can improve my syntax to avoid this issue, or is it just a bug that needs to be fixed? I've tried fetching other marks (e.g., first and last), but the only marks that ConTeXt seems to find are the ones for the left column. Thank you, Joey

2 4

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

ntg-context April 2020