February 2014 - ntg-context - NTG Mailing Lists

starttexdefinition error in standalone, works in TL2013
by Rik Kabel 12 Mar '14

12 Mar '14

The following code processes cleanly under TL2013 and fails with ConTeXt ver: 2014.02.14 17:07 MKIV beta fmt: 2014.2.16 int: english/english. I suspect a regression, but I am also open to being told that I am doing things incorrectly. I also notice that it fails (even under TL2013) if a space is inserted after [#SETUP] in the doTrans intro. I thought that spaces should be allowed in \starttexdefinition -- is this only in the body and not the parameter description? % macros=mkvi \showframe \let\EndTranslation\relax \starttexdefinition Trans \dosingleempty\doTrans \stoptexdefinition % The following should work, but fails with current beta \starttexdefinition doTrans [#SETUP]#TRANSLATION\EndTranslation \language[en] \doifsomething{#1}{\getparameters[TR][setup=,#SETUP]\TRsetup} \noindentation\blank[halfline] (\,\ignorespaces#TRANSLATION\removeunwantedspaces\,) \stoptexdefinition \starttexdefinition Translation \dosingleempty\doTranslation \stoptexdefinition % This version works with both Texlive and current standalone beta \def\doTranslation[#SETUP]#TRANSLATION\EndTranslation% {\language[en]% \doifsomething{#SETUP}% {\getparameters[TR][setup=,#SETUP]\TRsetup}% \noindentation\blank[halfline]% (\,\ignorespaces#TRANSLATION\removeunwantedspaces\,)% } \starttext Translation using \tex{def}{\tex{doTranslation}} works both with TL2013 and current beta. \Translation[language=en] It betrays a slow-witted mentality to pursue the streams, but not to see the sources of things. \EndTranslation \blank Translation using \tex{starttexdef doTrans} fails with current beta. \Trans[language=en] It betrays a slow-witted mentality to pursue the streams, but not to see the sources of things. \EndTranslation \stoptext -- Rik Kabel

3 4

Columns and clubpenalty problem
by Thomas Floeren 07 Mar '14

07 Mar '14

Hi, with the recent Betas, and the Current, I have a problem with columns and clubpenalty. In the following minimal the long item (item 1) will introduce a column break (instead of a simple line break): \def \defaultclubpenalty{\plustenthousand} \starttext \startitemize [columns] \item This is just a long line and should stay in the left column. \dorecurse{10}{\item bla bla bla} \stopitemize \stoptext Older ConTeXt versions work as expected (no column break in item 1), for example Beta 2013.11.13 12:28 or Current 2013.05.28 00:36. Thomas Floeren

2 3

Selectfont: extend and slant features
by Joshua Krämer 05 Mar '14

05 Mar '14

Dear list, the (fake) extend and slant features seem to be missing with Selectfont. Will they be made available sometimes in the future? Or am I simply doing something wrong? With simplefonts, they work. \definefontfeature [mainfeature] [default] [onum=yes] \definefontfeature [testfeature] [onum=no, extend=2, slant=0.25] \definefontfamily [mainfamily] [serif] [Latin Modern Roman] [features={mainfeature}] \setupbodyfont [mainfamily, 50pt] \starttext 1236 \addfeature [testfeature] 1236 \stoptext Kind regards, Joshua Krämer

3 8

\starthanging and hangafter
by Alan Bowen 03 Mar '14

03 Mar '14

I am using using \starthanging...\stophanging to embed a small image in a paragraph in a footnote. Currently, I have a pattern like: xxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Is there a way to get a pattern like xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx instead? Alan

3 7

Euler with fallback
by Aditya Mahajan 03 Mar '14

03 Mar '14

Hi all, This is to announce that the latest beta supports creating virtual math fonts with fallback. The main test case is to use Euler font with missing characters taken from Pagella but the mechanism is general and can be used to replace a specific set of math glyphs from a font. This feature is not extensively tested. As such it will be useful if everyone interested in math fallback mechanism could test this out and report any bugs or inconsistencies. To use this feature you have to use `pagellaovereuler` as your math font. For example, to use Euler with DejaVu fonts, use: \usetypescriptfile[euler] \starttypescript[mainface] \definetypeface[mainface][rm][serif][dejavu] [default] \definetypeface[mainface][ss][sans] [dejavu] [default] \definetypeface[mainface][tt][mono] [dejavu] [default] \definetypeface[mainface][mm][math] [pagellaovereuler][default] \stoptypescript \setupbodyfont[mainface] \appendtoks \rm \to \everymathematics \setupmathematics [lcgreek=normal, ucgreek=normal] There is a built-in typescript `euler-with-pagella` to use `pagellaovereuler` as the math font and `pagella` as the text font. If you are interested in implementing similar fallback mechanisms for other fonts, see type-imp-euler.mkiv and euler-math.lfg for details. Aditya

4 14

font handling
by Herbert Voss 03 Mar '14

03 Mar '14

I used uo-to-date minimal: \starttext test \stoptext voss@shania:/opt/context> pdffonts torus.pdf name type encoding emb sub uni object ID ------------------------ ----------- ----------- --- --- --- --------- WGBVOX+LMRoman12-Regular CID Type 0C Identity-H yes yes yes 18 0 \definefontfamily[Garamond][serif][Garamond Premier Pro] \setupbodyfont[Garamond] \starttext test \stoptext voss@shania:/opt/context> pdffonts torus.pdf name type encoding emb sub uni object ID ------------------------------ ----------- ---------- --- --- --- --------- RTODGH+LatinModernMath-Regular CID Type 0C Identity-H yes yes yes 18 0 The Garamond is not found which is no real problem here, but why do I get a math font here as default? Herbert

2 2

Plain format not building
by Philipp Gesang 02 Mar '14

02 Mar '14

Hi all, with the most recent Minimals (2014.02.14 17:07) building the Luatex Plain format no longer works: $ mtxrun --script plain --make ... mtx-plain | running command 'luatex --ini luatex-plain.tex \dump' This is LuaTeX, Version beta-0.78.2 (TeX Live 2014/dev) (rev 4746) (INITEX) \write18 enabled. (/home/phg/context/tex/texmf-context/tex/generic/context/luatex/luatex-plain.te x (/home/phg/context/tex/texmf/tex/plain/base/plain.tex Preloading the plain format: codes, registers, parameters, fonts, more fonts, ! Font \preloaded=manfnt not loadable: metric data not found or bad. <to be read again> \par l.468 ? Same when building manually. Can anyone reproduce this? Best, Philipp

2 2

(MkVI) Regression in named parameters, TL2013 to current
by Rik Kabel 01 Mar '14

01 Mar '14

% macros=mkvi \setupwhitespace[small] \def\ä<^>?z{Ä<^>?} \def\Named[#PARAMETERNAME]{¦#PARAMETERNAME¦} \def\Numbered[#1]{¦#1¦} \starttext \subject{Regression between TL2013 and current beta} There does appear to have been some change or regression in the definition of allowed characters in parameter names between the versions of TL2013 ({\tt ConTeXt ver: 2013.05.28 00:36 MKIV current fmt: 2013.12.11}) and the current standalone beta ({\tt ConTeXt ver: 2014.02.14 17:07 MKIV beta fmt:2014.2.14}) The definition \type{\def\Named[#PARAMETERNAME]{¦#PARAMETERNAME¦}} (using BROKEN BAR, U00A6) is processed without error and gives an acceptable result under TL2013. Under the current beta it fails. When warnings are skipped in the current beta, the generated PDF shows that the trailing BROKEN BAR appears to be treated as a part of the parameter name: \Named[value]. With numbered parameters (\type{\def\Numbered[#1]{¦#1¦}}), all is well in both versions: \Numbered[value]. This issue makes it difficult to convert macros that use delimiters (for example, \type{\def\ABC#1×#2¦{#1\ #2}}) to Mark VI syntax, and difficult to create such macros under Mark VI. \subject{What is allowed \ä<^>?z} What characters are acceptable in Mark VI parameter names? What characters are acceptable in Mark IV and Mark VI macro names? The wiki states: \quotation{Mark VI is identical to Mark IV in every respect, except that when you define a new macro you can give parameters names instead of numbers.} Other than that, there is no guidance. Experimentation shows that many more characters are allowed in \CONTEXT{} identifiers than are generally allowed with other \TeX{} engines. The definition providing the last part of the subject of this section, \type{\def\ä<^>?z{Ä<^>?}}, presents no problems. (That definition fails in Lua\TeX, \pdfTeX, and \XeTeX. I have never used Mark II, and do not have Ruby installed to enable a test.) -\hbox{}-~\crlf Rik Kabel \stoptext

3 4

unknown script 'context.lua' or 'mtx-context.lua
by Tim Li 01 Mar '14

01 Mar '14

Hi guys, I haven't played with ConTeXt for three month because of my examinations. Today, I delete the old version and reinstall a new one from the ConTeXt garden, but it seems that the new one can't run successfully. It says that unknown script 'context.lua' or 'mtx-context.lua. The error messages is the following: mtxrun | forcing cache reload resolvers | resolving | looking for 'texmfcnf.lua' on given path '/home/peng/texmf/web2c' from specification 'home:texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/bin/' from specification 'selfautoloc:' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/bin/share/texmf-local/web2c' from specification 'selfautoloc:/share/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/bin/share/texmf/web2c' from specification 'selfautoloc:/share/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/bin/texmf-local/web2c' from specification 'selfautoloc:/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/bin/texmf/web2c' from specification 'selfautoloc:/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/' from specification 'selfautodir:' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/share/texmf-local/web2c' from specification 'selfautodir:/share/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/share/texmf/web2c' from specification 'selfautodir:/share/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/texmf-local/web2c' from specification 'selfautodir:/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/texmf/web2c' from specification 'selfautodir:/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path './../texmf-local/web2c' from specification 'selfautoparent:/../texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on weird path './' from specification 'selfautoparent:' resolvers | resolving | looking for 'texmfcnf.lua' on given path './share/texmf-local/web2c' from specification 'selfautoparent:/share/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path './share/texmf/web2c' from specification 'selfautoparent:/share/texmf/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path './texmf-local/web2c' from specification 'selfautoparent:/texmf-local/web2c' resolvers | resolving | looking for 'texmfcnf.lua' on given path './texmf/web2c' from specification 'selfautoparent:/texmf/web2c' resolvers | resolving | resolvers | resolving | warning: no lua configuration files found resolvers | resolving | no texmf paths are defined (using TEXMF) resolvers | resolving | mtxrun | the resolver databases are not present or outdated resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'mtx-context.lua' resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'mtx-contexts.lua' resolvers | resolving | remembered file 'mtx-context.lua' resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'mtx-t-context.lua' resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'mtx-t-contexts.lua' resolvers | resolving | remembered file 'mtx-t-context.lua' resolvers | resolving | using suffix based filetype 'lua' resolvers | resolving | remembering file 'context.lua' mtxrun | unknown script 'context.lua' or 'mtx-context.lua' Best wishes, Tim

2 1

Strange behaviour with columnar itemized text
by Thangalin 01 Mar '14

01 Mar '14

Hi, I encountered two issues where itemized text within columns behaves unexpectedly. There appear to be two issues, possibly related. I will provide the shorter example first, which produces overlapping text on the second page (http://i.imgur.com/zMW6yk4.png) Changing \blank[.2em] to \blank[small] resolves the first issue. Removing inbetween={\blank[small]}, resolves the second issue. Given that changing the \blank command affects the results, I think they might be related somehow. I'm not concerned about the first issue -- changing ".25em" to "small" is fine. The second issue, however, leaves me perplexed for a solution to avoid the issue while maintaining the desired vertical whitespace (see (http://i.imgur.com/n46zEhf.png) between items. Any suggestions? Hopefully these are sufficiently minimal examples. ------------] 8< overlapping text 8< [------------ \setuphead[section][before={\testcolumn[3]},] \defineitemgroup[Instructions][inbetween={\blank[.25em]},] \starttext \startmixedcolumns[ align=right, balance=yes, grid=strut, ] \dorecurse{5}{ \startsection[title={Section},] \startInstructions \item{Preheat the oven to 400°F}\item{Put a few cups of salt in a gratin dish and level it off}\item{Place a little of the prepared butter mixture snail butter in an empty shell (about a teaspoon) and then put a snail in after it}\item{Put another blob of the snail butter on top until the snail is no longer visible in the shell (about a teaspoon)}\item{Do this for the remaining shells a layer of snail butter the snail itself and another layer of snail butter}\item{Now, push all the prepared shells into the salt in the gratin dish such that the shell openings are securely face up}\item{Make sure the shells to stay securely face up so that the snail cooks in the snail butter instead of the butter just leaking out}\item{If you have some special escargot dishes you can place the shells in them instead of the salt and gratin dish}\item{Ensure that the shells remain securely face up so that the snail cooks in the snail butter} \stopInstructions } \stopmixedcolumns \stoptext ------------] 8< snip snip 8< [------------ The second, slightly longer example, shows text overlapping the footer region (http://i.imgur.com/vUNyDmk.png) and extending off the second page. ------------] 8< snip snip 8< [------------ \setuppapersize[letter][letter] \definestartstop[RecipeIngredientGroup] \definestartstop[RecipeInstructionGroup] \defineitemgroup[RecipeIngredients] \defineitemgroup[RecipeInstructions][ inbetween={\blank[small]}, ] \setupstartstop[RecipeIngredientGroup][ before={\startmixedcolumns[balance=yes,]}, ] \setupstartstop[RecipeInstructionGroup][ before={\startmixedcolumns[grid=strut,]}, ] \setupstartstop[RecipeIngredientGroup,RecipeInstructionGroup,][ after={\stopmixedcolumns}, ] \starttext \startRecipeIngredientGroup \startsubsection[title={Title},] \startRecipeIngredients \dorecurse{32}{\item{item}} \stopRecipeIngredients \stopsubsection \stopRecipeIngredientGroup \startRecipeInstructionGroup \startsubsection[title={Title},] \startRecipeInstructions \dorecurse{8}{\item{item}} \stopRecipeInstructions \stopsubsection \startsubsection[title={Title},] \startRecipeInstructions \dorecurse{32}{\item{item}} \stopRecipeInstructions \stopsubsection \stopRecipeInstructionGroup \stoptext ------------] 8< snip snip 8< [------------

1 1