ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Bowen <bowenalan03@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt Standalone contents
Date: Fri, 10 Feb 2012 12:04:24 -0500	[thread overview]
Message-ID: <CAFMOkGWKr16OPYAb-4ZVspFGvAk4ZiOxkRHqErw2R_he7fTe4Q@mail.gmail.com> (raw)
In-Reply-To: <CAG5iGsBh8s=6WA+y-jAmNf5cN7X81Pz75X8u=z1ifkBprTiEVA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1666 bytes --]

Thanks, Luigi. I did indeed see it. But I am now having second thoughts. If
that is the closet one can get to a list, and given how the font-components
are scattered, perhaps I should work the other way and build a new personal
texmf directory, making additions as needed, rather than trimming the one
that I currently have.

A.

On Fri, Feb 10, 2012 at 11:37 AM, luigi scarso <luigi.scarso@gmail.com>wrote:

> On Fri, Feb 10, 2012 at 5:33 PM, Alan Bowen <bowenalan03@gmail.com> wrote:
> > I am currently in the process of moving the production of our journal and
> > book series from MKII to MKIV and suspect that I now have items in my
> > personal texmf folder that are no longer needed because they are
> included in
> > the distribution installed using sh //first-setup.sh --modules=all.
> >
> > So I was wondering if there was a listing somewhere of the fonts that
> come
> > ready to use with MKIV in the ConTeXt Standalone distribution. Any
> pointers
> > would be greatly appreciated. I have checked the wiki but have not yet
> found
> > what I am looking for.
> have you seen  type*.mkiv and type*.mkvi inside the  base/ folder ?
>
>
> --
> luigi
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________

[-- Attachment #1.2: Type: text/html, Size: 2515 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2012-02-10 17:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 16:33 Alan Bowen
2012-02-10 16:37 ` luigi scarso
2012-02-10 17:04   ` Alan Bowen [this message]
2012-02-10 17:27     ` luigi scarso
2012-02-10 18:19       ` Alan Bowen

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=CAFMOkGWKr16OPYAb-4ZVspFGvAk4ZiOxkRHqErw2R_he7fTe4Q@mail.gmail.com \
    --to=bowenalan03@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).