January 2016 - ntg-context - NTG Mailing Lists

font style query
by dr. Hans van der Meer 14 Jan '16

14 Jan '16

Some fonts as for example Lucida have a calligraphic style called up with \cg. If it is not present a default is taken. However, I would like to take other action in that case, for example switching to another font. Thus, how to test on the presence of that calligraphic style in the current font? Hans van der Meer

2 1

tooltip and buttom for footnotes?
by Ursula Hermann 14 Jan '16

14 Jan '16

Hello Wolfgang or Hans? Can one of you help me please. Iwant something like this: \setuppapersize[S6][S6] \setupinteraction[state=start] \setupcolors[state=start] \starttext Here is an example: by saying \type{\tooltip[left]{Example}{Is it nice}}, we get \blank \midaligned{\tooltip[bottom]{Example}{Isn't it nice?}} \blank This file when opened in Adobe Acrobat will show the tooltip "Isn't it nice?" when one hovers over the word "Example". \blank \midaligned{\tooltip[bottom]{an example}{Isn't it nice?} of tooltip on the bottom} \blank \midaligned{an example of tooltip on the \tooltip[right]{right}{Isn't it nice?}} \blank \midaligned{\tooltip[left]{an}{Isn't it nice?} example of tooltip on the left} \stoptext But i would need it for footnotes in pdf. Is this possible, or do I have to define somehting? Thanks Uschi

1 0

fontname
by dr. Hans van der Meer 14 Jan '16

14 Jan '16

I want to display the name of the current (body)font. \fontname{#1} should do the trick but what parameter to use? \currentfont \bodyfont \currentbodyfont are all wrong. Eevn the book "fonts in context" didn't help me out. What to use? Hans van der Meer

3 2

\doiftext vs. \doifemtpy
by Pablo Rodriguez 14 Jan '16

14 Jan '16

Dear list, which is the difference between \doiftext and \doifempty? Many thanks for your help, Pablo -- http://www.ousia.tk

3 2

(beta) missing /Shading entry in page /Resources
by Peter Rolf 13 Jan '16

13 Jan '16

Hi, I attached a minimal test file and the old (working) and new (broken) PDF files. The '/Shading 4 0 R' entry is missing in the page /Resources object ('10 0 obj <</ProcSet[/PDF]>> endobj') of the 'new' version. mtx-context | ConTeXt Process Management 0.63 mtx-context | mtx-context | main context file: v:/tmp/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2016.01.13 09:42 Best wishes, Peter

1 0

Bug in command \framed
by Jannik Voges 12 Jan '16

12 Jan '16

Hello, it seems that the command \framed in the newest beta (from today?) is buggy. Minimal example: \starttext \framed{bla} \stoptext Best wishes Jannik

4 4

\startalignment
by Alan BRASLAU 12 Jan '16

12 Jan '16

Hello, Jean-Michel pointed out to me the following curiosity: \starttext \input tufte \startalignment[middle] \input ward \stopalignment \input tufte \stoptext The startalignment applies to the preceding text, too. Strange... I never noticed this before as I have the habit of coding \startalignment\stopalignment blocks set-off with leading and trailing blank lines for better readability. But such practice could lead to undesired results. Consider the following example: \setupwhitespace [big] \starttext \input tufte \startalignment[middle] \input ward \stopalignment \input dawkins \stoptext So \stopalignment implicitly imposes a \par. If I were to omit the blank line before \startalignment so that no big whitespace be included before the centered block, the tufte text will get middle aligned. Also, perhaps I might not wish for the dawkins text to be separated by a big whitespace, logically as in: \startparagraph \input tufte \startalignment [middle] \input ward \stopalignment \input dawkins \stopparagraph Indeed, curious behavior. Alan

3 4

suddenly run error
by dr. Hans van der Meer 12 Jan '16

12 Jan '16

A document that runs fine under ConTeXt ver: 2015.10.09 21:28 MKIV beta fmt: 2015.10.11 int: english/english suddenly doesn't under ConTeXt ver: 2015.12.22 10:50 MKIV beta fmt: 2015.12.27 int: english/english mtx-context | fatal error: no return code, message: luatex: execution interrupted Loaded this beta today. The previous beta runs ok, the new beta gives the error. The pdf produced in the latter seems at fault. Anyone knows how this error can occur?

3 4

context zip files
by Hans Hagen 12 Jan '16

12 Jan '16

Hi, Due to a change in the structure: if you install / update context from the zip file make sure you first wipe you old tex/context and metapost/context paths. 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

font scaling does not work in footnotes
by massifr＠fastwebnet.it 12 Jan '16

12 Jan '16

Hello list, I have a problem with font scaling (see "sc=SansCaps sa 1.5" below). I'm using MyriadPro as sans font, but it lacks small caps. So I decided to provide them using AlegreyaSansSC, because it's similar to MyriadPro and it's made of small caps only. When I use \ss and \sc I get AlegreyaSC instead of MyriadPro. I want to scale them differently to balance their weights. That's why I wrote "sc=SansCaps sa 0.95". In body text the two fonts are balanced, but in the footnotes the scaling is ignored. What am I missing? Here's (part of) the typescript: \starttypescript [sans] [meo] \definefontsynonym [Sans] [name:MyriadPro-Regular][features=meo,fallbacks=mancanti] \definefontsynonym [SansBold] [name:MyriadPro-Bold][features=meo,fallbacks=mancanti] \definefontsynonym [SansItalic] [name:MyriadPro-It][features=meo,fallbacks=mancanti] % ... \definefontsynonym [SansCaps] [name:AlegreyaSansSC-Medium][features=meo,smcp,fallbacks=mancanti] \definebodyfont [13pt,11pt,10pt,8pt,7pt,6pt] [ss] [tf=Sans sa 0.85, it=SansItalic sa 0.85, bf=SansBold sa 0.85, bi=SansBoldItalic sa 0.85, sl=SansSlanted sa 0.85, sc=SansCaps sa 0.95] \stoptypescript Thank you, Massi

1 0