ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Tom" <Tom@tuxedo-press.com>
To: <ntg-context@ntg.nl>
Subject: Is Minimals ready for non-developers to use? (Tom)
Date: Mon, 14 Mar 2011 16:10:00 -0400	[thread overview]
Message-ID: <006001cbe283$ccb46a40$661d3ec0$@com> (raw)

Thank you for explaining this, Mojca. Knowing that it will be fixed sometime before September gives me hope. In the meantime, I think I have a workaround that, although awkward, will create a correct PDF. What I will do is create a PDF that is correct except for the TOC that Context generates, create a correct TOC PDF with another tool, then create a new PDF with the good pages from the original PDF and the bad TOC replaced by the good one.

Is there a list of known bugs somewhere? That would eliminate a lot of frustration and your having to deal with problems that are already being handled.

Is it possible for one to create a new font style? For example, if I have a need for two different sanserif fonts (Iwona and Helvetica for the sake of argument) to be used sporadically throughout a document. It would be nice to be able to do something like \ss1 to select the first one and \ss2 to select the second one. \ss to select the first one and \aa (or two other letters) to select the other.

Thanks,

Tom Benjey
717-258-9733 voice
717-243-0074 fax
blog: www.TomBenjey.com




-----Original Message-----
From: Mojca Miklavec [mailto:mojca.miklavec.lists@gmail.com] 
Sent: Monday, March 14, 2011 2:56 PM
To: mailing list for ConTeXt users
Cc: Tom
Subject: Re: [NTG-context] Is Minimals ready for non-developers to use? (Tom)

On Mon, Mar 14, 2011 at 14:22, Tom wrote:
> Dalyoung,
>
> To the contrary, You have been most helpful. Installing the latest version
> of Minimals worked fine but I wonder why they even advertise that there is a
> stable version to be downloaded.

When minimals were created, a new "stable" version was released
approximately once a week. It used to be a problem to get the beta
version working since beta often depended on a new version of luatex
(which was also released every two/three weeks, but often not
synchronized with ConTeXt releases).

Now Hans only releases a stable version twice a year or so. The
problem is that minimals have not been designed with that in mind and
there is only a single version of texmfcnf.lua and only a single
version of luatex binary. Consequently minimals can only work either
with beta or with current when the two versions diverge, but not with
both and beta has priority.

I need to change the way the distribution works entirely, from the
grounds up (I have many parts ready, but not ready to publish yet).

An easy solution would be to create another mirror and only provide a
working current version there.

> I guess they mean a stable version of MKII.
> I had the same experience that you had with the Introduction not showing up
> in the TOC. Do you know how to report a bug?

You don't need to report it. I'm aware of that flaw. I could do a
temporary fix, but I would prefer to fix it properly. I'm sorry that
it alredy took me several years to address those issues, but I promise
to fix it before the conference. Properly.

You also need to keep in mind that even though it is advertized as
stable, bugs won't be fixed (many project often have at least two
branches of development - one for fixing the released version and one
for real development; the released version should get bugfixes, but in
context development that doesn't and won't happen unless some
volunteer starts carefully checking the new code and only applies
bugfixes to the stable version).

So most people that use ConTeXt actively need bugfixes very often and
the only way to get the bugs fixed is to use the latest version. Well,
latest version comes with its own bugs, but at least you have a chance
to get them fixed quickly.

Mojca

___________________________________________________________________________________
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
___________________________________________________________________________________


             reply	other threads:[~2011-03-14 20:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 20:10 Tom [this message]
2011-03-14 20:17 ` Mojca Miklavec
     [not found] <mailman.1401.1300033032.4223.ntg-context@ntg.nl>
2011-03-14  9:16 ` Jeong Dalyoung
2011-03-14 13:22   ` Tom
2011-03-14 18:55     ` Mojca Miklavec

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='006001cbe283$ccb46a40$661d3ec0$@com' \
    --to=tom@tuxedo-press.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).