- ntg-context - Mailing Lists

next beta
by Hans Hagen 25 Feb '16

25 Feb '16

Hi, The next beta will have a more efficient metafun filldraw option named 'fillup' (flaw and drill were rejected as operator names): \starttext \startMPpage fill fullsquare scaled 4cm withpen pencircle scaled 1cm; draw fullsquare scaled 4cm withpen pencircle scaled 1cm; \stopMPpage \startMPpage fillup fullsquare scaled 4cm withpen pencircle scaled 1cm; \stopMPpage \stoptext The second page will have more efficient pdf code. The beta also has some new arrow trickery that Alan will reveal at the next context meeting. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

1 0

issue with \sethyphenatedafter
by Pablo Rodriguez 25 Feb '16

25 Feb '16

Dear list, I have the following sample: \sethyphenatedurlafter{/} \define[1]\mypersonalurl{{\tt\goto{\hyphenatedurl{#1}}[url(#1)]}} \starttext \hsize\zeropoint \mypersonalurl{http://contextgarden.net} \stoptext Using latest beta from 2016.02.20 14:55, I get: http :/ / contextgarden .net Is there any way to force the two slashes to be on the same line? Many thanks for your help, Pablo -- http://www.ousia.tk

2 7

Re: [NTG-context] docbook(5) to context conversion
by David Nebauer 25 Feb '16

25 Feb '16

On 23/02/16 06:33, Jan Tosovsky wrote: > On 2016-02-22 David Nebauer wrote: >> Are there any publicly available solutions for converting >> docbook/docbook5 to context? ... >> >> * dbcontext >> - part of dblatex, abandoned ~10 years ago > I used this way some time ago, but it required tweaks in approx 10 xslt files to make it compatible with Context MkIV Cool. Any chance you could post your amended xslt files to give a newbie a head start? > Some general tweaks were sent to the original author who promised merging them. He also mentioned planned update in the near future... Since then dbcontext has been removed from the dblatex distribution. The current dblatex is 0.3.7 but it looks like the most recent dbcontext is from 0.2pre. I think the chances of dbcontext getting further love from its author are not good... David.

3 2

Disappearing \rrbracket
by Nicola 24 Feb '16

24 Feb '16

I have a problem with the symbol in the subject. This is a minimal document: \starttext $\llbracket x\rrbracket$ $\bigl\llbracket x\bigr\rrbracket$ $\Bigl\llbracket x\Bigr\rrbracket$ $\biggl\llbracket x\biggr\rrbracket$ $\Biggl\llbracket x\Biggr\rrbracket$ \stoptext Using ConTeXt from TeX Live 2015, \rrbracket is rendered only in the first case (current beta is ok). Can you reproduce this? Is there a workaround? Nicola

3 3

Re: [NTG-context] ntg-context Digest, Vol 140, Issue 59
by Aidan Nichol 24 Feb '16

24 Feb '16

Thanks for the reply. \thispage is producing no output in all the places it is being invoked Aidan > On 24 Feb 2016, at 15:35, ntg-context-request(a)ntg.nl wrote: > > startsetups[referenceformat:thispage] > \doifelse{\filterreference{page}}{\rawcountervalue[userpage]} > {{\tttf !?}} > {\filterreference{page}} > \stopsetups > > \definereferenceformat[thispage][setups=referenceformat:thispage] > > \starttext > > \chapter[one]{First chapter} > > First: \thispage[one] > > Second: \thispage[two] > > \chapter[two]{Second chapter} > > First: \thispage[one] > > Second: \thispage[two]

1 0

Re: [NTG-context] PDF Inclusion Regression
by Christoph Reller 24 Feb '16

24 Feb '16

On Wed, Feb 24, 2016 at 4:38 PM Hans Hagen <pragma(a)wxs.nl> wrote: > > On 2/24/2016 2:23 PM, Christoph Reller wrote: > > I am afraid but this might be a bug in newer versions of luatex. I would > > greatly appreciate if this would be addressed. > > fixed in next luatex release Thank you very much, Hans! -- Christoph

1 0

PDF Inclusion Regression
by Christoph Reller 24 Feb '16

24 Feb '16

Hi, I have found the following problem when including an external PDF with \externalfigure: Some (or all?) values in PDF arrays that are between -1.0 and 0.0 loose their minus sign. E.g: -0.1 turns into 0.1. This can lead to significant visual differences. This problem did not exist in earlier versions of ConTeXt. For a MWE consider the following: \starttext \externalfigure[test.pdf] \stoptext where test.pdf is attached and has a MediaBox [-0.1 -0.1 612 792]. In the PDF produced by ConTeXt test.pdf is correctly put in an XObject but this XObject now has a BBox [0.1 0.1 612 792]. I am afraid but this might be a bug in newer versions of luatex. I would greatly appreciate if this would be addressed. Kind regards, Christoph

2 1

size in setuptype
by Meer, Hans van der 24 Feb '16

24 Feb '16

Why does \setuptyping has a parameter bodyfont= and is \setuptype missing it? I am asking because in typesetting with \setuptype[style=small]\type{something} I get another font and size than with \setuptyping[bodyfont=small]\starttyping ... \stoptyping whereas in both the same is wanted in order to keep continuity in size and style. \setuptype[bodyfont=small] definitely gave something different, i.e. no change. \setuptype[bodyfont=small]: can this be incorporated in the next ConTeXt-beta producing the same effect as \setuptyping[bodyfont=small]? It would be very nice. Hans van der Meer

2 3

Controlling \at output
by Aidan Nichol 24 Feb '16

24 Feb '16

I’m trying to create something (like varioref in latex) that suppresses \at output if the referenced item is on the current page. The main decision point is with \doifelse{\at[ref2]}{\rawcountervalue[page]}{ same page }{ different page } no matter what I try (expdoifelse and other ways to get the current page) the values never match. \doifelse{\at[ref2]}{\at[ref1]}….. (ref1 and ref2 are on the same page but don’t match \doifelse{\rawcountervalue[page]}{1}… it is page 1 but always fails. The only match I get is with \doifelse{\at[ref2]}{\at[ref2]}…. which is pretty useless Presumably I’m doing something stupid. Or do i have to go for a much lower level approach

2 1

Re: [NTG-context] two issues with interactive hyperlinks (please comment)
by Christoph Reller 23 Feb '16

23 Feb '16

Hi Hans, First and foremost: Thank you for uploading the Beta! This solves the problem I have reported with \reference and focus=standard: https://www.mail-archive.com/ntg-context%40ntg.nl/msg79620.html On Tue, Feb 23, 2016 at 12:00 PM Hans Hagen <pragma(a)wxs.nl> wrote: > > On 2/23/2016 12:21 AM, Pablo Rodriguez wrote: > > > I think that (futhermore not being a default) ConTeXt should implemente > > what is an ISO standard nowadays. > > well, i have been quite active in implementing what pdf provided and > constantly had to adapt to what acrobat finally implemented (often the > standard was ahead) and > ... > I agree with you and Pablo: the ISO standard is what counts. And I believe that named destinations, their use, and viewer behavior is described there clearly. ... so one handicap for me is that i won't make test docs for it > I will try to provide minimal examples that I believe are so common that the viewer behavior should be clear. ... > > And sorry, not being the default, why is wrong reading pages in fit to > > width mode? > > that one still has to make sure that there is a reasonable view area (so > that one sees what went and comes) ... i'm not sure how you handle it > but esp jumping from page to page in a fit width mode is quite annoying; > fit width actually makes sense when one makes each chapter (or section) > into one long page and i actually played with it but i found no viewer > capable to keep the same scale each page > I believe that many people have to make compromises, e.g., cannot afford the time or money to produce both a screen version and a print version of a document. I believe that the fit-width mode is a good compromise - as long as it is viewed in "continuous" viewing mode. ... > > Is there anything that I can do to help? I’m especially interested in > > this feature. > > small few page examples with predictable positioning and predictable > spacing (btw, footnotes will always be sort of a pain as they are > rendered in special ways, but footnotes should be forbidden anyway; if > a doc is also for screen endnotes are way better) > I agree with you about footnotes. And, as mentioned above, I will try to come up with decent example documents. There are still cases in my documents that don't work and i will try to minimize these. Thanks again for your effort! Christoph

2 1