dev-context July 2007

dev-context@ntg.nl

4 participants
3 discussions

metafun: colored dotlabel fails (fix included)
by Sanjoy Mahajan 25 Jul '07

25 Jul '07

In metafun, a colored dotlabel fails. A fix is included below. Here is a minimal test file: beginfig(1) dotlabel(btex etex, origin) withcolor green; endfig; end It produces this error: $ mpost -mem=metafun t This is MetaPost, Version 0.993 (Web2C 7.5.6) (t.mp ! Extra tokens will be flushed. <to be read again> withcolor l.2 dotlabel(btex etex, origin) withcolor green; ? [I'm using the metafun that was built from context 2007.04.17.] Metapost used to have this problem, for which John Hobby sent the following updated definition of dotlabel(): vardef dotlabel@#(expr s,z) text t_ = label@#(s,z) t_; interim linecap:=rounded; draw z withpen pencircle scaled dotlabeldiam t_; enddef; It is part of the current plain.mp (mpost 0.993). But the metafun.mp format-generation file includes mp-base.mp, which has the old definition of dotlabel: vardef dotlabel@#(expr s,z) = label@#(s,z); interim linecap:=rounded; draw z withpen pencircle scaled dotlabeldiam; enddef; The patch below fixes the minimal test case above as well as the larger real file that I started with: --- a/metapost/context/base/mp-base.mp 2007-07-25 00:19:15.379198092 -0400 +++ b/metapost/context/base/mp-base.mp 2007-07-25 00:19:37.072411646 -0400 @@ -477,10 +477,10 @@ def label = draw thelabel enddef; newinternal dotlabeldiam; dotlabeldiam:=3bp; -vardef dotlabel@#(expr s,z) = - label@#(s,z); +vardef dotlabel@#(expr s,z) text t_ = + label@#(s,z) t_; interim linecap:=rounded; - draw z withpen pencircle scaled dotlabeldiam; + draw z withpen pencircle scaled dotlabeldiam t_; enddef; def makelabel = dotlabel enddef;

2 1

[contexttest-Bugs][78] additional blank line in starttyping environment
by contexttest-bugs＠foundry.supelec.fr 16 Jul '07

16 Jul '07

Bugs item #78, was opened at 2007-07-16 23:39 You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=161&aid=78&group_id=21 Or by replying to this e-mail entering your response between the following markers: #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ (enter your response here) #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ Status: Open Priority: 3 Submitted By: Peter Münster (peter) Assigned to: Nobody (None) Summary: additional blank line in starttyping environment Category: macros Version: None Resolution: None Initial Comment: Hello, when using align=flushleft and \typebuffer in \framed, additional space is introduced at the top. Example: \setupcolors[state=start] \setuptyping[before=,after=] \startbuffer bla \stopbuffer \starttext \framed[background=color,backgroundcolor=red]{\typebuffer} \framed[align=flushleft,background=color,backgroundcolor=red]{\typebuffer} \stoptext Cheers, Peter ---------------------------------------------------------------------- You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=161&aid=78&group_id=21

1 0

[Fwd: Re: urgent bib bug]
by Taco Hoekwater 12 Jul '07

12 Jul '07

Hi all, Can someone please have a look at this for me? I have to run off for TUG2007 now (ye, already), and I could not discover what is wrong. The problem seems to be with false positives from \doifcurrentlevelelse, but that is the only thing I could discover til now. Thanks in advance, Taco -------- Original Message -------- Subject: Re: urgent bib bug Date: Wed, 11 Jul 2007 19:09:00 -0600 From: Idris Samawi Hamid <ishamid(a)colostate.edu> Organization: Colorado State University To: Taco Hoekwater <taco(a)elvenkind.com> References: <op.tvbhx2vfnx1yh1@your-b27fb1c401> <469541C5.80200(a)elvenkind.com> Hi, On Wed, 11 Jul 2007 14:47:01 -0600, Taco Hoekwater <taco(a)elvenkind.com> wrote: > Please send me a short (as short as possible, but complete) example > and perhaps I can fix it tomorrow. But I must warn you: I did not do > anything to the module in months, and there is no new context release, > so I am absolutely clueless as to what could be going wrong. Here is a directory which should work out of the box; test file is bib-test.tex. I think I found the key to the problem: For \title, the entry of the previous \title is repeated. For \chapter it behaves correctly. I define my articles in terms of \title, and each article is within a \start-stopproduct file. So basically the bib-module needs to support \title as well (used to do so). Best wishes Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523 -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

dev-context July 2007