- ntg-context - NTG Mailing Lists

page numbering 'marginedge'
by David Wooten 03 Mar '14

03 Mar '14

Hello all, trying to get page numbers in the outer margin edge of a double-sided document — marginedge as it is places the numbers to the inside margin edge, is there an opposite command? Thanks, David

3 2

\placefigure[right or left] failing in footnotes
by Alan Bowen 03 Mar '14

03 Mar '14

The following does not work as it should: setupexternalfigures[location={local,default}] \starttext text% \footnote{\hangsidefloat[2] \placefigure[right,none]{} {\externalfigure[cow][width=.1\textwidth]} \dorecurse{3}{\input ward}} %for comparison \hangsidefloat[2] \placefigure[right,none]{} {\externalfigure[cow][width=.1\textwidth]} \dorecurse{3}{\input ward}% \stoptext The text and image in the main body are as they should be. But note that the first line of the footnote is blank and that, while the image is placed as it should be, the text runs through it. I am running ConTeXt ver: 2014.02.14 17:07 MKIV beta. Alan

2 2

\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

Trying to use my local otf math font by editing typescript
by 罗晨星 03 Mar '14

03 Mar '14

Hi here. I was trying to use my own math font in Mark IV, inside distribution TeX Live 2013, using typescript, but failed. The way I am thinking, I might use an fallback way. For most of the math symbols, I would use the provided palatino stuff, but for MathRoman and MathItalic, I'd like to use the same font as of normal text, let's say Minion Pro. As I'm looking into a normal typescript file, I thought of a few options: First of all, just overwrite the Palatino typescript, like follows: \starttypescript \definefontsynonym [MathRoman] [name:minionproregular] \definefontsynonym [MathItalic][name:minionproit] \stoptypescript It gives out "Math error: parameter \Umathquad\displaystyle is not set ..." Another way I'm trying, is to use some fall back mode. \starttypescript [math] [palatino] \setups[font:fallback:math] \definefontsynonym [MathRoman] [name:minionproregular] \definefontsynonym [MathItalic][name:minionproit] \stoptypescript It also doesn't work. The result was same as the previous. And I also tried \starttypescript [math] [palatinofb] \usetypescript[math][palatino] \definefontsynonym [MathRoman] [name:minionproregular] \definefontsynonym [MathItalic][name:minionproit] \stoptypescript This also makes no difference. Inspired by http://tex.stackexchange.com/questions/150566/minionpro-including-math-in-c…, I also tried the \definefallbackfamily, it turn out to be an undefined control sequence. In the main typescript, I uses \definetypeface[MinionPro-Mixed][mm][math][palatino][default] So I cannot find out how to fulfill my need. I guess there might because of a missing map file, but for a roman font, do we need any? Since the following serif definition works fine: \definefontfeature[zh][mode=node,script=hang,lang=zhs] \starttypescript [serif] [MinionPro-Mixed] \definefontfallback[Serif] [name:minionproregular][0x0000-0x0400][force=yes] \definefontfallback[SerifItalic] [name:minionproit] [0x0000-0x0400][force=yes] \definefontfallback[SerifBold] [name:minionprobold] [0x0000-0x0400][force=yes] \definefontfallback[SerifBoldItalic][name:minionproboldit] [0x0000-0x0400][force=yes] \definefontsynonym [Serif] [name:fzshusongz01][fallbacks=Serif] [features=zh] \definefontsynonym [SerifItalic] [name:fzheib01][fallbacks=SerifItalic] [features=zh] \definefontsynonym [SerifBold] [name:fzheib01][fallbacks=SerifBold] [features=zh] \definefontsynonym [SeriBoldItalic] [name:fzheib01][fallbacks=SerifBoldItalic] [features=zh] \stoptypescript As I've seen, normally, a fallback definition of typescript is used in serif/sans/mono, but there comes no successfull example for fall back of math font. Also, there is fall back for a font, but not an entire typescript. And build a new math font is obvious beyond my competent. So how to deal with this problem? Is there a solution? Regards, 南京大学现代工程与应用科学学院 2013级罗晨星 Luo Chenxing ————————————— chenxing.luo(a)gmail.com

3 2

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

Re: [NTG-context] Footnote mark gap
by Wolfgang Schuster 01 Mar '14

01 Mar '14

Am 28.02.2014 um 19:56 schrieb Jan Tosovsky <j.tosovsky(a)email.cz>: > On 2014-02-27 Wolfgang Schuster wrote: >> Am 27.02.2014 um 23:19 schrieb Thangalin <thangalin(a)gmail.com>: >> >>> Try: >>> >>> \setupfootnotes[ >>> textstyle={\hskip.05em}, >>> ] >> >> It's better to add the space with the textcommand key. >> >> \setupnote[footnote][textcommand={\hairspace\high}] > > Thanks! I was trying \hskip on \setupnotation[footnote] before as I though > this command is preferred in MkIV. My fault. The \setupnotation command replaced the old \setupnotedefintion command and a few setting like counter related values moved from \setupnote to \setupnotation but the layout of the numbers in the text body is still controlled by \setupnote. > When I saw 'hairspace' I was afraid the footnote mark can wrap to the next > line, but after some tests it seems to be a false assumption. Yes, \hairspace is a unbreakable space and will kep the number together with the last word. Wolfgang

1 0

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