- ntg-context - Mailing Lists

graphics
by Hans Hagen 13 Dec '18

13 Dec '18

Hi, As most mechanism are reasonable okay now we can look into what future versions of ConteXt should provide in terms of functionality. The (luatex) engine is also more of less finished or at least stable in terms of functionality. One possible area of further development is graphics so I'd like to know if there are (reasonable) demands for more graphics support using metapost. Alan and I are on-and-off working on some extensions and one of the things we discuss is visualization of data. The question is of course what should be done in the lua/mp/tex combination and what externally but the combination has some advantages. There has been presentations and discussions at the last meeting and graphics is always a nice topic, and also kind of rewarding in terms of development. Of course other demands can be formulated too, but these then need to come with well defined descriptions (or mockup examples). 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 -----------------------------------------------------------------

9 28

Drops Module
by Aditya Mahajan 13 Dec '18

13 Dec '18

Hi Peter, I noticed that the drops module recently stopping running with the error: /home/adityam/texmf/tex/context/third/drops/t-drops.lua:1098: bad argument #3 to 'format' (number has no integer representation) stack traceback: [C]: in function 'string.format' /home/adityam/texmf/tex/context/third/drops/t-drops.lua:1098: in upvalue 'get_IM_paths' /home/adityam/texmf/tex/context/third/drops/t-drops.lua:1380: in field 'shadow' [ctxlua]:1: in main chunk This is due to the change in Lua5.3 with respect to floating point numbers. The simplest solution is to change '%d' to '%.0f' at appropriate places. Thanks, Aditya

2 1

\startnarrower
by Hans van der Meer 13 Dec '18

13 Dec '18

Is it possible to not indent the very first line of narrower content? Thus \startnarrower first line second line etc. \stopnarrower resulting in: first line second line etc. dr. Hans van der Meer

2 1

\xmlfunction
by Hans van der Meer 12 Dec '18

12 Dec '18

How can one transmit argument values to \xmlfunction in order to be used by the Lua function called? dr. Hans van der Meer

1 0

finding content of xml elements
by Hans van der Meer 12 Dec '18

12 Dec '18

Having a string pointing to an element in the XML-tree, for example IDENT::3 as the third element of the tree IDENT. How can access this element in a Lua function as function examine(element)…end called with value element = IDENT::3? Or formulated otherwise: how can I reach from that string into the XML-tree? dr. Hans van der Meer

1 0

modifying kerning breaks opentype ligatures (and other features)
by mf 12 Dec '18

12 Dec '18

Hello list, i noticed that setting a different kerning breaks some features of opentype fonts; that is true, for example, for ligatures and fractions (frac feature). It looks like a modified kerning inserts something between two adjacent character, making them no more adjacent. That way the lookup of opentype tables fails. "f", "l" => "fl" ligature glyph "f", [kerning], "l" => distinct "f" and "l" glyphs "1", "/", "4" => "¼" glyph (with "frac" feature switched on) "1", [kerning], "/", [kerning], "4" => distinct "1", "/", "4" glyphs (always with "frac" feature switched on) MWE: \definecharacterkerning[narrow][factor=-.015] \definecharacterkerning[wide][factor=.015] \definefontfeature[frac][frac=yes] \starttext \feature[+][frac]% Some ligatures: float, finance, affine; a fraction: 1/4. \setcharacterkerning[narrow]Some ligatures: float, finance, affine; a fraction: 1/4. \setcharacterkerning[wide]Some ligatures: float, finance, affine; a fraction: 1/4. \stoptext In my XML to PDF workflow, fractions are marked up, so it's easy to switch the kerning off only for them. Instead i have no solution for ligatures: parts of text with a modified kerning loose ligatures, and i end up with the same words, once with ligatures, once without, even in the same page. Is there a workaround for this? Massimiliano

3 10

repo.or.cz/context.git
by Henri Menke 12 Dec '18

12 Dec '18

Dear list, There is an online browsable repo with the ConTeXt sources at https://repo.or.cz/context.git It seems to be extremely outdated, the latest commit says beta 2014.02.14 17:07. I know that there is an up-to-date mirror at https://github.com/contextgarden/context-mirror but the Wiki links to the one at repo.or.cz. Could you either update the repo.or.cz mirror or adjust the Wiki to link to GitHub please? Cheers, Henri

1 0

External Figure add caption or alternative text for tagged pdf/x
by Kelley, Claire 11 Dec '18

11 Dec '18

Hi All. I am trying to embed an image in a pdf so that when you open the pdf in acrobat or another reader the image is correctly tagged as an image and there is alternative text. So far I am able to export the back end tags so that I can see tags on tables and paragraphs, but the image comes through tagged as a paragraph and I am unable to add any alternative text. This is the code I am using: \setupbackend [format=PDF/X-1a:2001, export=yes] \externalfigure[district.pdf][height=10cm] Does anyone have any idea how I could fix this? Thanks! Claire

1 0

issue with optical bounds (OpenType)
by Pablo Rodriguez 10 Dec '18

10 Dec '18

Dear list, I’m experiencing a weird issue with optical bounds in OpenType. Here you have the mandatory sample (font avaiable at https://gitlab.com/ousia/greek-lfbd/raw/master/TypographicaOStandard-Regula…) \startluacode fonts.handlers.otf.addfeature { name = "leftbounds", type = "single", data = { Ἀ = { -32, 0, -32, 0 }, Ἁ = { -32, 0, -32, 0 }, Ἂ = { -70, 0, -70, 0 }, Ἃ = { -70, 0, -70, 0 }, Ἄ = { -50, 0, -50, 0 }, Ἅ = { -50, 0, -50, 0 }, Ἇ = { -42, 0, -42, 0 }, Ἆ = { -42, 0, -42, 0 }, Ἠ = { -212, 0, -212, 0 }, Ἡ = { -212, 0, -212, 0 }, Ἢ = { -258, 0, -258, 0 }, Ἣ = { -258, 0, -258, 0 }, Ἥ = { -286, 0, -286, 0 }, Ἤ = { -286, 0, -286, 0 }, Ἦ = { -246, 0, -246, 0 }, Ἧ = { -246, 0, -246, 0 }, Ὧ = { -196, 0, -196, 0 }, } } \stopluacode \enabletrackers[fonts.protrusion] \definefontfeature[default][default] [script=greek, protrusion=quality, opbd=yes] \definefontfeature[leftbounds][leftbounds=yes] \showframe \setuplayout[page] \definefontfamily[mainface][rm][Typographica Old Standard] \definefontfamily[mainface][tt][Latin Modern Mono] \setupbodyfont[mainface, 300pt] \setupalign[hanging] \startbuffer \ifnum\pagenumber=1{\ttxx opbd}\else{\ttxx -opbd}\fi\page Ω\\ Ὧ\\ Α\\Ἀ\\Α\\Ἁ\\Α\\Ἂ\\Α\\Ἃ\\Α\\Ἄ\\Α\\Ἅ\\Α\\Ἆ\\Α\\Ἇ\\ Ἠ\\Η\\Ἡ\\Η\\Ἢ\\Η\\Ἣ\\Η\\Ἤ\\Η\\Ἥ\\Η\\Ἦ\\Η\\Ἧ\\Η \stopbuffer \starttext \getbuffer \setupalign[nothanging] \feature[+][leftbounds] \getbuffer \stoptext OpenType optical bounds are read from the font right: fonts > protrusions > left factor 1, right factor 1 fonts > protrusions > setting left using lfbd fonts > protrusions > lfbd -> 0.032 Ἀ (U+01F08) fonts > protrusions > lfbd -> 0.032 Ἁ (U+01F09) fonts > protrusions > lfbd -> 0.070 Ἂ (U+01F0A) fonts > protrusions > lfbd -> 0.070 Ἃ (U+01F0B) fonts > protrusions > lfbd -> 0.050 Ἄ (U+01F0C) fonts > protrusions > lfbd -> 0.050 Ἅ (U+01F0D) fonts > protrusions > lfbd -> 0.042 Ἆ (U+01F0E) fonts > protrusions > lfbd -> 0.042 Ἇ (U+01F0F) fonts > protrusions > lfbd -> 0.196 Ὧ (U+01F6F) fonts > protrusions > lfbd -> 0.246 Ἧ (U+01F2F) fonts > protrusions > lfbd -> 0.286 Ἦ (U+01F2E) fonts > protrusions > lfbd -> 0.246 Ἥ (U+01F2D) fonts > protrusions > lfbd -> 0.258 Ἤ (U+01F2C) fonts > protrusions > lfbd -> 0.286 Ἣ (U+01F2B) fonts > protrusions > lfbd -> 0.258 Ἢ (U+01F2A) fonts > protrusions > lfbd -> 0.212 Ἡ (U+01F29) fonts > protrusions > lfbd -> 0.212 Ἠ (U+01F28) I’m afraid that they aren’t applied accurately. The same values are used with the property "leftbounds" and they are perfect in that feature. Shouldn’t be the output from both methods be exactly the same? In all glyph pairs, both accented and unaccented glyphs should end in exactly the same point. I think this may be a bug, although I may be missing something. Many thanks for your help, Pablo -- http://www.ousia.tk

2 10

Spurious missing character reports
by Rik Kabel 10 Dec '18

10 Dec '18

List, I have one document that after the 2018-11-18 update (beginning with 12-01 and continuing to the current 12-07) has generated hundreds of spurious missing character messages in the log. A short extract: fonts > start missing characters: C:/ConTeXt/tex/texmf/fonts/opentype/public/antt/AntykwaTorunskaCond-Regular.otf fonts > 72 U+00021 ! EXCLAMATION MARK fonts > 948 U+00022 " QUOTATION MARK fonts > 1302 U+00026 & AMPERSAND fonts > 345318 U+0002B + PLUS SIGN fonts > 216 U+00030 0 DIGIT ZERO fonts > 54270 U+00031 1 DIGIT ONE fonts > 28590 U+00036 6 DIGIT SIX fonts > 414 U+0003C < LESS-THAN SIGN fonts > 116712 U+00040 @ COMMERCIAL AT fonts > 1980 U+00042 B LATIN CAPITAL LETTER B fonts > 373878 U+00046 F LATIN CAPITAL LETTER F fonts > 48 U+00048 H LATIN CAPITAL LETTER H fonts > 3282 U+00049 I LATIN CAPITAL LETTER I fonts > 36 U+0004A J LATIN CAPITAL LETTER J fonts > 1560 U+0004B K LATIN CAPITAL LETTER K fonts > 12 U+0004C L LATIN CAPITAL LETTER L fonts > 3810 U+0004E N LATIN CAPITAL LETTER N fonts > 3402 U+00057 W LATIN CAPITAL LETTER W fonts > 48 U+0005A Z LATIN CAPITAL LETTER Z fonts > 64206 U+0005B [ LEFT SQUARE BRACKET fonts > 3420 U+00062 b LATIN SMALL LETTER B fonts > 3888 U+00063 c LATIN SMALL LETTER C fonts > 2880 U+00069 i LATIN SMALL LETTER I fonts > 1284 U+0006B k LATIN SMALL LETTER K fonts > 336 U+00070 p LATIN SMALL LETTER P fonts > 2118 U+0007B { LEFT CURLY BRACKET fonts > 258 U+0007C | VERTICAL LINE fonts > 12 U+0007E ~ TILDE fonts > stop missing characters There are similar reports for the other fonts used in the document (Antykwa Torunska is used for heads, EBGaramond with Libertinus fallback for the body). I have pared down the files to the following example which demonstrates the problem. I do not understand now all the features interact to cause this, but the reports disappear upon removing any (such as the seemingly-redundant \definebodyfontenvironment or the \switchtobodyfont[small]). \enabletrackers [fonts.missing] \definebodyfontenvironment [11pt] [a=1] \definefontfallback [fb:ebgr] [file:libertinusserif-regular] [0x204A] \starttypescript [serif] [ebgaramond] \definefontsynonym [Serif] [file:ebgaramond-regular] [fallbacks=fb:ebgr] \stoptypescript \define\Test{¡Missing!} \setupbodyfont [ebgaramond,11pt] \setupbodyfont [libertinus,11pt] \starttext \dorecurse{6}{ \switchtobodyfont[small] \Test\par} \stoptext While the messages appear to be incorrect, there is no apparent problem associated with them. I do not know if they point to some problem I have not recognized, or are truly spurious. (And I can eliminate them by turning off the tracker when I am sure that I have the needed coverage in the fallbacks.) Of course, if I am doing something wrong I would like to correct it. -- Rik

2 1