From: Duncan Hothersall <dh@capdm.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: mkii to mkiv - what an ancient user needs to know
Date: Wed, 12 Jun 2019 09:32:24 +0100 [thread overview]
Message-ID: <CAN8fp9Xx6t-KvPCMCDmXAbp=yM__rOu88Rk0B90vV-zuZeRQSA@mail.gmail.com> (raw)
In-Reply-To: <a1547669-52b8-621b-ee2e-f446736f94ce@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2387 bytes --]
Thanks Hans, that's good to know. I was seeing issues which seemed to be
related to setupheader statements using command=, which are in heavy use in
our system because we use this to externalise styles. But it could easily
have been something font-related left in some of the commands.
I will work on a minimal example over the next few days and - if I don't
solve it myself in the process - I'll post it.
Thanks again,
Duncan
On Wed, 12 Jun 2019 at 08:07, Hans Hagen <j.hagen@xs4all.nl> wrote:
> On 6/12/2019 5:22 AM, Duncan Hothersall wrote:
> > Hi all.
> >
> > Long-time user but haven't posted in a long while...
> > **
> >
> > After many happy years of running a mkii set up I am finally facing the
> > fact that time has moved on and upgrading to mkiv.
> >
> > I understand the biggest change needed to my sources is in the fonts
> > handling, but I am getting a few other problems with things like
> > chapter/sectioning setups that I can't see mentioned in
> > https://www.contextgarden.net/MkIV_Differences
> >
> > I was wondering if there exists a comprehensive "what you have to change
> > in your sources to move from mkii to mkiv" document anywhere or, failing
> > that, if anyone can offer guidance on what has changed in the
> > chapter/sectioning setups code between the two.
> >
> > Apologies for not supplying an example of code - I'm not yet at the
> > point that that's possible.
> >
> > Any help much appreciated. And hello to anyone who remembers me from
> > fifteen plus years ago!
> Do you get errors? There should be no real fundamental differences
> betwene mkii and mmkiv wrt the interfac, but because font encodings are
> gone and input is utf8 by default that might need to be changed.
> Structure has more options. I think the biggest conceptual change in the
> setups has been the way footnotes are configured. Of course there are
> new commands too.
>
> So, a small example triggering the issue would help,
>
> Hans
>
> ps. Of course the biggest change is that luatex is used instead of
> pdftex/xetex.
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
>
[-- Attachment #1.2: Type: text/html, Size: 3588 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-06-12 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 3:22 Duncan Hothersall
2019-06-12 7:07 ` Hans Hagen
2019-06-12 8:32 ` Duncan Hothersall [this message]
2019-06-12 14:22 ` Hans Hagen
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='CAN8fp9Xx6t-KvPCMCDmXAbp=yM__rOu88Rk0B90vV-zuZeRQSA@mail.gmail.com' \
--to=dh@capdm.com \
--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).