- ntg-context - NTG Mailing Lists

Search path for typescripts
by Rik Kabel 01 Mar '19

01 Mar '19

List, What is the proper place to put a custom typescript file to make it accessible to multiple projects? For testing I placed copies in" 1) the local directory 2) <user>/texmf/fonts 3) <installation>/tex/texmf-local/fonts/ A standard version (uncustomized) exists as part of the distribution in: 4) <installation>/tex/texmf-context/tex/context/fonts/mkiv/ luatools <typescriptfile> finds the file in 1, 4, and 2. That is, after the local directory it immediately takes the standard installation directory, never looking in the places one might store local versions meant to override the distribution files. It might get to one of those directories (<user>/texmf/fonts) if there is no standard file in the distribution, but that is not the case here. I did not see an appropriate environment variable to control this. It does not seem sensitive to TEXMF or OSFONTDIR. So, where do I place the customized typescript, or how do I tell ConTeXt where to look? -- Rik

2 2

em-dash ligature is converted to en-dash in the generic fontloader
by Marcel Krüger 01 Mar '19

01 Mar '19

On 2/23/2019 1:50 PM, Ulrike Fischer wrote: > As reported on the dev-luatex list --- is converted to an en-dash > (instead of em-dash) if there are no spaces around the ---. > > We could now reproduce the problem also with the generic fontloader: > it appears only with mode=node. I'm using the files from 2019-02-14, > but the problem appeared first in the files from 2018-11-18): > > \font\test={file:texgyreheros-regular.otf:+tlig;mode=node;}\test > > dashes-these % gives dash > > dashes--these % gives en-dash > > dashes---these % gives en-dash WRONG > > dashes --- these % gives em-dash > > em-dashes---these % gives em-dash > > \bye > > context is not affected, there the code works fine. This issue can be fixed in the fontloader with the attached patch. Best regards, Marcel Krüger

3 5

TeX Live 2019: attempt to call a nil value (upvalue 'isfile')
by Henri Menke 01 Mar '19

01 Mar '19

Dear list, I just installed TeX Live 2019 pretest and running context --make fails with error in callback: ...xlive/2019/texmf-dist/tex/context/base/mkiv/luat-cod.lua:194: attempt to call a nil value (upvalue 'isfile') This can easily be fixed by replacing in luat-cod.lua local isfile = lfs.isfile with local isfile = function(file) return lfs.attributes(file,"mode") == "file" end This should probably be fixed before the release. Cheers, Henri

4 8

How to define a new language?
by Paul Hoffman 01 Mar '19

01 Mar '19

I'm trying to define a new language for use in a bilingual document, but my hyphenation patterns are being ignored and I'm sure I must be doing something wrong. I've devised a minimal example that should hyphenate between vowels but doesn't. Here's the hyphenation patterns file: ----------------------------- lang-foo.pat ----------------------------- % Hyphenation patterns for Foo. \begingroup \patterns{ a1a a1e a1i a1o a1u e1a e1e e1i e1o e1u i1a i1e i1i i1o i1u o1a o1e o1i o1o o1u u1a u1e u1i u1o u1u } \endgroup ------------------------------------------------------------------------ I tried to convert this to Lua code but couldn't figure out the right invocation of _mtxrun --script pattern --convert_. Then I wrote a minimal Context file and hoped it would pick up lang-foo.pat anyhow: ----------------------------- test-foo.tex ----------------------------- \installlanguage[foo][ spacing=broad, leftsentence=---, rightsentence=---, leftsubsentence=---, rightsubsentence=---, leftquote=\upperleftsinglesixquote, rightquote=\upperrightsingleninequote, leftquotation=\upperleftdoublesixquote, rightquotation=\upperrightdoubleninequote, date={month,\ ,day,{,\ },year}, state=stop, ] \mainlanguage[foo] \setuppapersize[A6] \setupalign[hyphenated,morehyphenation,flushleft] \starttext umleoeoikaoukkoiiaaiewuewniimoaralkokolwwuiuirmlkipetnoaeteuntoilooooamm uuuauemepokawpoieoomtkeaipeailloaukoiwaeuaewurawiueanwtaoaoemmuuonwleaue mrtmuweokmikariurtlluiraapnkowuaueolmrneraiiioeauemmaamauiiolluwrltounte aaaunnoitwueemwlniowotuauwomaupaapwtawiikiuolnrolouletouunwptoioououoael kiitinouoeolopewourtuineuaermnmmioaiuienkewuiaaklinipprurainouioiomuwokr koriiaieulkppwwieoemlipiakinppprnpaiaaekapnpatritotoeormaetualeonemlppau earoeauoiimekoilliiuomirnrwarpupieiilaaueeoaekwriummikpatakeairolwpiaoaa tniweuiineeetuiektpalukluanetoiklwnemutlonnuaalpnelpniiuiutmaoakmkoiomia ineioporrieopatakomonipiuwuiwiiaueiueoluoeaaiootwuekinkwawrrwwppilewoioo itroreraeonkeuiaawalunnueoreiaaeewknailaeomomilkruruekuonkaonwwiieunonow \stoptext ------------------------------------------------------------------------ It does seem to see lang-foo.pat: $ context --pdf test-foo.tex | fgrep patterns mkiv lua stats > loaded patterns: en::2 foo::67, load time: 0.000 But in the resulting PDF, nothing is hyphenated. (I'll post the PDF if anyone really wants to see it.) Here's my _context --version_ output: mtx-context | ConTeXt Process Management 1.02 mtx-context | mtx-context | main context file: /usr/local/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2018.01.19 13:42 Can someone point me to my mistake? Thanks in advance, Paul. -- Paul Hoffman <nkuitse(a)nkuitse.com>

3 4

Modes and conditional part of the source
by Procházka Lukáš Ing. 01 Mar '19

01 Mar '19

Hello, I'm struggling with using modes to make a part of the text conditional. Here is my code: ---- \def\b#1{\startmode[#1]} \def\e{\stopmode} % \enablemode[100] % For optional usage \starttext A \b{100} % Should be start of some conditional text from here ... B \e % ... to here \stoptext ---- Compilation fails with: " tex error > tex error on line 0 in file : ! Emergency stop <*> cont-yes.mkiv <empty file> *** (job aborted, no legal \end found) " How to make the sample work? Best regards, Lukas -- Ing. Lukáš Procházka | mailto:LPr@pontex.cz Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz | IDDS: nrpt3sn | IČO: 40763439 Bezová 1658 147 14 Praha 4 Mob.: +420 702 033 396

4 4

Output problem with nodes.toutf utility function (latest beta 02.26.2019)
by Joseph Canedo 28 Feb '19

28 Feb '19

Dear list, I use lua function nodes.toutf to print text being typeset in log output for debugging purposes etc… and I noticed output is now different for some characters/glyphs. I use EB Garamond font, which might explain. Before, for example output was : user > margin > margin box text Thareh. Now it is : user > margin > margin box text 󰀙areh. The « Th » was replaced by some 󰀙 placeholder perhaps for unknown character? Please note that typeset text is not impacted, it seems correct. Joseph

3 3

Distance between two Columns
by Ursula Hermann 28 Feb '19

28 Feb '19

Dear List! I have the following example. I would like to have two columns that are in the distance small. So I have tried: \setuppapersize[A5] \startcolumns \defineframed [tightframed][width=5cm,width.1\textwidth,align=right] \tightframed{Small} \column \tightframed{A really really long line that is split at 5cm} If I take the example with only \tightframed, without the columns, I have the small distance, but I would like to have a left and right column with small distance. Can someone help me please?

3 2

Setting tabulate table width with \textwidth inside an item group
by Clyde Johnston 27 Feb '19

27 Feb '19

Dear List: I have a tabulate table inside an indented item group and I would like to set the width of the table to the \hbox size of the surrounding text. If I use \textwidth as a width parameter, the table spills into the right margin (see attached). What is the correct parameter to use to set the width of the table to the width of the text in the item group? MWE \starttext \showframe \startitemize[n,3*broad] \startitem{% \input ward \starttabulate[|cp(.25\textwidth)|cp(.75\textwidth)|] \HL \NC Column A \NC Column B \NC \NR \HL \NC 1 \NC 2 \NC \NR \NC 2 \NC 3 \NC \NR \NC 3 \NC 4 \NC \NR \NC 4 \NC 5 \NC \NR \NC 5 \NC 6 \NC \NR \BL \stoptabulate \input ward } \stopitem \stopitemize \stoptext Thanks, Clyde

2 2

Footnotes being broken over two pages
by Lars 27 Feb '19

27 Feb '19

Hi there, I've stumbled upon some behaviour that looks like a bug to me. Sometimes longer footnotes are being broken over two pages. Please see the attached picture: As you can see the last footnote on p. 6 is being continued on p. 7. I don't think it's a problem of too many footnote lines on one page as on p. 17 there are more lines and the breaking is in order. The code for all links that I create like this is: \define\NytAsimov{ \goto{ \hyphenatedurl{ https://www.nytimes.com/1992/04/12/business/technology-a-celebration-of-isa… [url(https://www.nytimes.com/1992/04/12/business/technology-a-celebration-of…] (Abrufdatum 12.12.2018)} The line breaking I only did for readability. In my source all those definitions are in single lines. Does anyone have an idea why this is happening? If you need anything just let me know please. Thanks in advance, Lars.

2 2

horizontal headalternatives ignore indentnext
by Henri Menke 27 Feb '19

27 Feb '19

Dear list, If I choose the headalternative to be of horizontal type, e.g. “text”, the head placement will ignore the indentnext option. This can be traced back to the \strc_rendering_stop_placement macro where there is a check \ifconditional\headisdisplay \useindentnextparameter\headparameter \else \ignoreparskip \noindentation % recently added, was a bug \fi If the headalternative is vertical, \headdisplay is true, if it is horizontal, \headdisplay is false. It is easy to see that indentnext is not treated on equal footing for these two, in fact, indentation is generally ignored for horizontal headalternatives. Commenting out \noindentation at least gives indentation in the following paragraph but that is not a proper solution. Below you can find a MWE with the fix from above applied. Try commenting in and out the \noindentation and see what happens to the second paragraph after the heading. Cheers, Henri --- \unprotect \def\strc_rendering_stop_placement {\n_strc_rendering_hang_lines\zerocount \ifconditional\headisdisplay \strc_rendering_initialize_line_hang % kind of special, we want to snap heads also according to local specs local \setbox\b_strc_rendering_head\hbox {\hskip\dimexpr\d_strc_rendering_local_leftoffset+\headparameter\c!margin\relax \box\b_strc_rendering_head \getheadsyncs % a latelua why not in the box }% \ifgridsnapping \applygridmethod {\headparameter\c!grid}% {\ifconditional\headisdisplay \strc_rendering_initialize_style_and_color_display\c!textstyle\c!textcolor \fi}% {\box\b_strc_rendering_head} \else \box\b_strc_rendering_head \fi \flushnotes % new, not really needed \endgraf \ifvmode \ifnum\n_strc_rendering_hang_lines>\zerocount \dorecurse\n_strc_rendering_hang_lines{\nointerlineskip\dosomebreak\nobreak\strut\endgraf}% to be checked \fi \nointerlineskip \dosomebreak\nobreak \fi % \getheadsyncs % a latelua why not in the box \else % somehow this goes ok even when we push in the margin probably because we gobble pars % in the process of collecting index entries etc \strut \flushnotes % new, here since we're in par mode \unhbox\b_strc_rendering_head \getheadsyncs % a latelua \ifconditional\headissomewhere \strc_sectioning_stay_on_this_line % test case: alternative=margintext and \startparagraph .. \else %\hskip\headnumberdistance\s!plus\headnumberdistance\s!minus.25\dimexpr\headnumberdistance\relax \hskip\headtextdistance\relax \strc_sectioning_inject_continuous_signal \fi \fi \ifconditional\headisdisplay \ifvmode \ifgridsnapping % important, font related depth, see comment \prevdepth\strutdp \else \prevdepth\d_strc_rendering_local_depth \fi \fi \fi \synctexpopline \egroup \egroup \ifconditional\headisdisplay \useindentnextparameter\headparameter \else \ignoreparskip % \noindentation % recently added, was a bug \fi} \protect \setupindenting[yes,big] \setuphead[section][alternative=text,indentnext=yes] \starttext \section{Introduction} \input knuth \stoptext

1 0