- ntg-context - Mailing Lists

ANN: Updated Vim scripts for ConTeXt
by Nicola 21 Oct '16

21 Oct '16

Hello, attached you find an update of the Vim scripts for ConTeXt. A few highlights: - jump commands ([[, ]], [{, ]}, ...); - jump to file included with \project, \component, etc... by typing gf when the cursor is above the filename; - tp (TeX paragraph) text object (e.g., use gqap to reflow a paragraph); - i$ and a$ text objects; - better integration with MetaPost (indentation and autocompletion inside \startMP...\stopMP... works automatically); - syntax highglighting can be enabled for any nested filetype (MetaPost and Lua are enabled by default); - compiler plugin, supporting mtxrun and Makefiles; - Asynchronous typesetting with :ConTeXt command. I plan to submit these changes for inclusion in Vim, but I'd like to get some feedback, especially re background typesetting and especially from Windows users. I recommend to test with Vim 8.0 patch 22 or later. Nicola

5 9

bug in font size switches?
by Pablo Rodriguez 20 Oct '16

20 Oct '16

Dear list, from the previous message from Csikos, I have generated the following sample: \setupbodyfontenvironment[default][a=5, x=8, xx=6] \starttext Default {\tfa Larger} {\tfx Smaller1} {\tfxx Smaller1} \\ Default \tfa Larger \tfx Smaller2 \tfxx Smaller2 \stoptext I can set a different value for a, but not for x or xx. The values for x and xx seem to be hardcoded. If this isn’t a bug, what am I missing here? Many thanks for your help, Pablo -- http://www.ousia.tk

4 7

font size switching
by Csikos Bela 20 Oct '16

20 Oct '16

Dear context users: It seems to me that some of the the font size switching commands do not work as described in the context reference manual (contextref.pdf, 27/09/2013), e.g. \tfx. The manual writes on page 109 that "Note that these commands select font sizes relative to the default, not relative to whatever font size is currently in eﬀect." But in my case \tfx switches to smaller compared to the size in effect, and not smaller compared to default size. In additions I couldn't find command for returning to default size after a font switching command. How to switch (back) to normal size? Here is an MWE: \starttext default, {\tfa larger (a)}, {\tfb larger (b)}, {\tfc larger (c)}, {\tfd larger (d)} default, {\tfx smaller (x)}, {\tfxx smaller (xx)} This is normal text, (default 10pt). {\tfa This is larger (a).} Normal again. {\tfx This is smaller, (x).} This is normal size. \bfa This is larger bold (a). \tf This is normal larger (a), \backslash tf doesn't change size. How to switch back to normal size, if there is no suffix for normal size? \tfx And why isn't this smaller (x) if the suffix changes size relative to default size as the manual states? \stoptext Thank you in advance, bcsikos

4 8

Reduced whitespace when nesting different itemgroups
by Florian Leupold 20 Oct '16

20 Oct '16

Dear list, I have noticed a strange behavior when nesting different itemgroups: The whitespace before the lower-level group is reduced. This does not happen when nesting itemgroups of the same kind. And this can somehow be circumvented by setting [columns, one], see MWE below. Is this expected behavior, or a bug? Best regards, Florian MWE: \starttext \startitemize \item Itemize 1. \startitemize[columns, one] \item Itemize 1.1 \item Itemize 1.2 \stopitemize \stopitemize \defineitemgroup[it] \startitemize \item Itemize 1. \startit \item It 1.1 (reduced whitespace above) \item It 1.2 \stopit \stopitemize \startitemize \item Itemize 1. \startit[columns, one] \item It 1.1 \item It 1.2 \stopit \stopitemize \stoptext

1 0

Re: [NTG-context] Systemwide installation does not work
by Roger Mason 20 Oct '16

20 Oct '16

Hello all, Alan Braslau <alan.braslau(a)cea.fr> writes: > After forcing a rebuild of the freebsd binaries and committing them to > the garden, first-setup.sh now seems to work correctly. Would you try > again installing on your system? > > I will try to see with Mojca what went wrong with the server: why > committing openbsd binaries overwrote the freebsd binaries. > > Sorry for any inconvenience. No apology required. On the contrary, thank you for the work you do in providing the binaries, it is very much appreciated. I can confirm that everything is now working again. Best wishes, Roger

3 2

Re: [NTG-context] Becoming a TeX/ConTeXt poweruser
by Jamie Macbeth 19 Oct '16

19 Oct '16

Will do. Thanks!

1 0

Re: [NTG-context] Becoming a TeX/ConTeXt poweruser
by Jamie Macbeth 19 Oct '16

19 Oct '16

Thank you Pablo and Hans for your answers on this!Jamie

1 0

xml: spurious empty spaces
by Thomas A. Schmitz 19 Oct '16

19 Oct '16

Hi all, below is a slightly silly example that demonstrates a problem I’m having: I want to process (in Lua) the xml element “b” only when it has an attribute “display” set. This works, but elements without the attribute leave spurious spaces in the pdf output. The workaround I’m currently using is if xml.attribute(e, "./", "display", "") ~= "yes" then context.unskip() else … but that seems like a kludge. Is this expected behavior, or should this be fixed? Thanks Thomas \startbuffer[test] <a> test test test test test test test </a> \stopbuffer \startxmlsetups xml:testsetups \xmlsetsetup{\xmldocument}{a|b}{xml:*} \stopxmlsetups \xmlregistersetup{xml:testsetups} \startluacode function xml.functions.b(e) xml.strip(e, "/", nolines, anywhere) if xml.attribute(e, "./", "display", "") == "yes" then context.space() context("/") context.space() lxml.flush(e) end end \stopluacode \startxmlsetups xml:a \xmlflush{#1} \stopxmlsetups \startxmlsetups xml:b \xmlfunction{#1}{b} \stopxmlsetups \starttext \xmlprocessbuffer{main}{test}{} \stoptext

2 2

blockquote oddity
by Alan Bowen 19 Oct '16

19 Oct '16

\starttext \startblockquote [w]hile we may [w]hile we may \stopblockquote \stoptext seems to fail with the latest beta (ConTeXt ver: 2016.10.14) unless one replaces the first line with \[w\]hile we may. The error message is tex error > tex error on line 4 in file /Users/bowen1/Desktop/TestTeX/test.tex: ! Missing number, treated as zero <to be read again> w \spac_narrower_method_analyze ...arrower_middle #1 \relax \fi \syst_helpers_repeat_with_command ..._again [#1]#5 \else \syst_helpers_repeat... \17>>1 ..._process_comma_list_with_parameters {#1} \syst_helpers_do_process_c... \syst_helpers_do_process_comma_list ...rgument #1, ]\relax \global \advance \... \spac_narrower_start_apply ...narrower_initialize \advance \leftskip \dimexp... ... l.4 [w]h ile we may 1 \starttext 2 3 \startblockquote 4 >> [w]hile we may 5 6 [w]hile we may 7 8 \stopblockquote 9 10 \stoptext 11 ? Alan

2 2

PDF/A generation
by Henri Menke 19 Oct '16

19 Oct '16

Dear list, (especially Luigi) for online publication I need to create a PDF/A compliant output file. Does anyone have any experience with it and can tell me whether my setup will work? So far I'm using \setupbackend [ format={pdf/a-2a}, profile={default_cmyk.icc,default_rgb.icc,default_gray.icc}, ] \setupstructure[state=start,method=auto] I chose PDF/A-2a because there I can have PDF 1.7 which keeps the file size down but I can also switch to PDF/A-1a. I have *no* external pixel graphics, just included PDFs which are also produced by ConTeXt with the same setup. Online I found Luigi's paper on PDF/A-1a [1]. However, even after reading I'm unsure whether `intent` is optional or required. Since I don't own Adobe Acrobat (nor am I using Windows) I cannot verify the resulting output. Does anyone know any working free or open-source tools for GNU/Linux to do this task? Cheers, Henri [1] http://www.ntg.nl/maps/41/08.pdf

4 12