From: Dave <confused.scientist@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: When to migrate from MKII to MKIV?
Date: Tue, 3 Feb 2009 17:51:15 -0500 [thread overview]
Message-ID: <7a884c7c0902031451x7cbca2bdle9fb92bc61e2c911@mail.gmail.com> (raw)
In-Reply-To: <6faad9f00902031414y3eb293e8m6bfe4ae42094ecc2@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1802 bytes --]
On Tue, Feb 3, 2009 at 5:14 PM, Mojca Miklavec <
mojca.miklavec.lists@gmail.com> wrote:
> If you neglect the bugs and problems, transition should be painless -
> only typescripts need to be updated, but once you do that, your
> documents could even work with both mkii and mkiv.
I recall that it took me a good week of work in the evenings to get my
regular and math typescripts to work correctly with MKII. I'm happy with
the PDF output of the papers/notes, lecture notes I write for work but I
will need to switch to OTF in the not-too distant future. My university has
a site license for various Adobe pro fonts but they are only being
distributed in OTF now. The ones I currently use were derived
from manipulating a set of multiple-masters a few years ago.
> Btw: math is a big mess at the moment; you can expect any kind of bugs
> related to maths with next beta version, but you can become a beta
> tester :)
>
I do physics/chemistry with a lot of equations so incomplete math support is
really a deal breaker for me. I recall there being issues with some aspects
of bibliography support and a lack of fonts when I last tried the Minimal
package. Again, deal breakers for me so I reverted to the ConTeXt included
in the 2008 version of texlive with a few bug-fixes from a more recent beta.
I think it would be very helpful to most ConTeXt 'users' if there were a
wiki page that spelled out the current status of MKIV exactly and listed
which features of MKII work, which are buggy, and which are work in
progress. Something a little more high-level than the release notes and
this mailing list ;)
Thank you to everyone who contribute here. I often find myself amazed at
the speed at which ConTeXt develops and very much look forward to the end of
font voodoo as promised by MKIV.
[-- Attachment #1.2: Type: text/html, Size: 2333 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-02-03 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 20:57 Dave
2009-02-03 21:34 ` Aditya Mahajan
2009-02-04 7:01 ` Alan BRASLAU
2009-02-04 8:03 ` Joseph Wright
2009-02-04 9:21 ` luigi scarso
2009-02-03 22:16 ` Mojca Miklavec
[not found] ` <6faad9f00902031414y3eb293e8m6bfe4ae42094ecc2@mail.gmail.com>
2009-02-03 22:51 ` Dave [this message]
2009-02-03 23:12 ` Hans Hagen
2009-02-03 23:23 ` Arthur Reutenauer
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=7a884c7c0902031451x7cbca2bdle9fb92bc61e2c911@mail.gmail.com \
--to=confused.scientist@gmail.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).