- ntg-context - NTG Mailing Lists

Lua os.date() localization in context
by Romain Diss 29 Apr '19

29 Apr '19

Hi all, I would like to print the day name of a date in french using my current locale. In lua I can do: > os.setlocale('fr_FR.UTF-8',all) > print(os.date("%A")) But in a cld document it doesn't work. Context complains about using "os.locale in a supposedly locale neutral enviroment" and it prints the day name in english. How can I translate the day names without hardcoding everything? Thanks in advance. Best. -- Romain Diss

1 0

Lua error in latest beta?
by Alan Bowen 29 Apr '19

29 Apr '19

When I process files using the latest standalone ConTeXt ver: 2019.04.29 08:52 MKIV beta fmt: LuaTeX, Version 1.10.0 (TeX Live 2019)), I now get the following error message: lua error > lua error on line 8 in file env_Brill-01.tex: ...eXt/tex/texmf-context/tex/context/base/mkiv/font-oup.lua:1317: bad argument #1 to 'concat' (table expected, got number) The error log is as follows: return { ["filename"]="env_Brill-01.tex", ["lastcontext"]="\ \\font_helpers_low_level_define ...nsize }{\\m_font_designsize }\\scaledfontmode \ \\relax \\ifcase \\scaledfont...\ \\font_fallbacks_clone_unique ...w_level_define {#1}\\v_font_identifier_basic \ \\csname \\v_font_identifier...\ l.8 }\ \ \\font_fallbacks_prepare #1->\\clf_fontcollectionprepare {#1}\ \ \\font_fallbacks_prepare_indeed ... \\lastrawfontcall \\font_fallbacks_prepare #1\ \\endgroup \ <inserted text> ...nt_fallbacks_prepare_indeed \\m_font_fallbacks \ \\fi \\fi \ ...\ l.215 \\setupbodyfont[mainface, 10pt]\ ", ["lastluaerror"]="...eXt/tex/texmf-context/tex/context/base/mkiv/font-oup.lua:1317: bad argument #1 to 'concat' (table expected, got number)", ["lasttexerror"]="?", ["linenumber"]=8, ["luaerrorline"]="1317", ["offset"]=10, } This files process as they should with earlier versions. I will try to produce an mwe if needed but hope that it is not. Alan

1 0

Re: [NTG-context] No menu bar option for Adobe Reader
by Paul Schalck 28 Apr '19

28 Apr '19

@Hans: Thanks a lot, I'm looking forward to testing it. @Alan: Like Hans said. It's a new option, and I have it activated in my local environment file. It's the only and clumsy way to control the interface setting since Adobe Reader cannot save the state of the menu bar permanently (which is complete nonsense). I use Acrord because I'm used to it and because I think it still has the best subpixel rendering, at least in the Linux world (with Wine). Mozilla's PDF.js comes close though. Paul

2 1

option=tex in setuptyping causes the background to be drawn twice
by Aditya Mahajan 28 Apr '19

28 Apr '19

Hi, The following minimal example: \definetextbackground [EXAMPLE] [ location=paragraph, rulethickness=1pt, leftoffset=5em, rightoffset=0mm, ] \setuptyping[option=tex, before=\startEXAMPLE, after=\stopEXAMPLE] \starttext \starttyping A = B + C \stoptyping \stoptext gives the attached output where the background is repeated twice. The bug is present with both mkiv and ltmx. Aditya

3 4

Question to lines in linetable
by Tomas Hala 28 Apr '19

28 Apr '19

Hi all, I tried linetable tables (mkiv, TL2017) because I need even horizontal splitting. It works fine but I do not know how to make either horizontal or vertical lines. Have somebody got some experience with this? Best wishes, Tomáš

2 2

Strange backgroundcolors with showgrid and luacode
by Otared Kavian 27 Apr '19

27 Apr '19

Dear all, When typesetting an old list of exercises, I noticed that when \showgrid is active and a luafunction is called, there is some unwanted and strange background colors (gray and blue, or yellow and blue). Thes background colors seems to show up on an unfilled page when a lua function is used, and I could come up with the following minimal example which gives the attached PDF. Could someone, please, tell me what I am doing wrong? Best regards: OK %%%% begin test-strange.tex \showgrid %\setuplayout[grid=yes] \startluacode AdditionTest = function(nn) local a = {} local b = {} for i = 1,nn do a[i] = i b[i] = nn - i end context.midaligned("\\bfa Exercises") context.blank() context.startcolumns { n = 3 } context.starttabulate { "|r|c|r|c|r|" } for i=1,nn do context.NC() context(a[i]) context.NC() context.mathematics("*") context.NC() context(b[i]) context.NC() context("=") context.NR() end context.stoptabulate() context.stopcolumns() context.page() end \stopluacode \starttext \ctxlua{AdditionTest(12)} % the background colors, gray and blue, show up when a lua function is called % \ctxlua{AdditionTest(120)} % the background colors, yellow and blue, show up when a lua function is called % \input knuth % the background colors do not show up here \stoptext %%%% end test-strange.tex

4 9

precompose combining characters
by Pablo Rodriguez 27 Apr '19

27 Apr '19

Dear list, I have the following sample: \setupbodyfont[gentium, 60pt] \starttext Combined: τῇ Precomposed: τῇ \stoptext Is there an automatic way in LuaTeX to get the precomposed character from combining ones without having to add a feature? Many thanks for your help, Pablo -- http://www.ousia.tk

1 0

suggestion for LMTX
by Pablo Rodriguez 27 Apr '19

27 Apr '19

Hi Hans, compiling the following sample with LMTX \starttext \contextmark \contextbanner \stoptext outputs MKIV. Wouldn’t LMTX be a better option than LMTX? Many thanks for your help, Pablo -- http://www.ousia.tk

2 2

problems with "pagecomment"
by Mohammad Hossein Bateni 27 Apr '19

27 Apr '19

Hi, Look at the following MWE: \setuppagecomment[state=start,location=right] %\definestartstop[Notes] %[before=\startpagecomment,after=\stoppagecomment] \def\startNotes{\startpagecomment} \def\stopNotes{\stoppagecomment} \starttext \input knuth \startpagecomment Hello \stoppagecomment \page \input tufte \startNotes Testing \stopNotes \stoptext This snippet does not compile. Page comments work when I use the commands \startpagecomment and \stoppagecomment directly (like in the first page), but when I invoke via macros (as in the second page), ConTeXt produces errors. What is wrong there? Thanks! ~MHB

2 2

wrong intraword spacing
by Pablo Rodriguez 27 Apr '19

27 Apr '19

Dear list, I have the following sample: \definefontfeature [default] [default] [itlc=yes] \setupitaliccorrection [always] \setupbodyfont %~ [heros] %~ [pagella] [termes] \starttext \startTEXpage[offset=1em] \em Dr. Steffan \stopTEXpage \stoptext After the ligature, there is an unwanted extra space. Could anyone confirm the issue (I get it with both latest betas LMTX and MkIV)? Many thanks for your help, Pablo -- http://www.ousia.tk

3 4