From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: To update or not to update - that is the question...
Date: Sat, 02 Mar 2013 11:29:09 +0100 [thread overview]
Message-ID: <5131D475.401@wxs.nl> (raw)
In-Reply-To: <20130302011135.30edce68@aga-netbook>
On 3/2/2013 1:11 AM, Marcin Borkowski wrote:
> I have an issue with \overrightarrow being positioned under its
> argument. I've read on the list that this is now fixed, but... I
> can't upgrade! This is because I'm preparing a document in an
> "incremental" way, that is, I'm preparing course materials (problem
> sets) for the next class each week and giving them away to students.
> If I upgrade, the pagebreaks change (probably due to some tweaking Hans
> added to multicolumn itemgroups a few months ago). So what would you
> suggest? I can see at least three solutions, none of which is ideal for
> me.
No clue when you updated ..
> 1. Manually backport the fix to my ConTeXt. Pro: ideal solution (at
> least for now). Con: no idea how to do it - I don't know how to
> access ConTeXt repository (if it's at all possible for a non-developer).
You could try to backport but be warned that the arrow macros have been
changed because of more possibilities in the open type fonts (so there
is a relationship with fonts too).
> 2. Upgrade and insert some manual pagebreaks so that pages 21-22 (which
> I'm currently working on) contain the same problems as they used to.
> Pro: easy fix. Con: very dirty trick, and what if someone asks me
> about some old problems, because he lost his copy?
Why don't you use version numbers and store pdf files? After all, it's
quite normal that educational materials get updated. Also, use
references to numbers instead of pages.
The recent reimplementation of arrows was stand-alone and the old
math-arr.mkiv code is still there so you can try to load that file.
> 3. Just use \vec instead of \overrightarrow. Pro: very easy, no dirty
> hacks. Con: ugly looking (see: \vec{AB}).
> Any ideas? Is it possible to find the official ConTeXt repo somewhere,
> or if not, maybe someone could send me the diff of the commit which
> fixed that (this post:
> http://article.gmane.org/gmane.comp.tex.context/79011 suggests that it
> is the 2012.10.30 21:13 commit)?
I don't know if Mojca still keeps old betas and checks them in in her
public git repos.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-03-02 10:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 0:11 Marcin Borkowski
2013-03-02 10:29 ` Hans Hagen [this message]
2013-03-17 14:04 ` Marcin Borkowski
2013-03-02 11:04 ` Marco Patzer
2013-03-17 14:05 ` Marcin Borkowski
2013-03-17 23:22 ` Jonathan Barchi
2013-03-18 9:20 ` Marco Patzer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5131D475.401@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).