ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: afsmith <adventurecomplete@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: MKIV, fonts, confusion
Date: Wed, 13 May 2009 09:31:19 -0700	[thread overview]
Message-ID: <5df5befa0905130931u35f777eh102b0ef94c5ec2ea@mail.gmail.com> (raw)
In-Reply-To: <5df5befa0905130618j570c02a5k687b3aea95fa89c0@mail.gmail.com>

Luigi, Hans, and Wolfgang, thank you for your responses. I'm still
unclear on several things. (comments on your responses follow
afterwards)

Let me try asking these things as questions. Specifically, could
someone please tell me...
1. How do I determine whether I am using MKII, MKIV, or XeTeX to
process my documents?
2. Given the line from a typescript...
\definefontsynonym[LiberationSerif] [name:liberationserif]
... how do I determine which file "name:liberationserif" corresponds to?
3. In both MKII and MKIV, how can I determine which typescripts exist?
In other words, how do I determine working arguments for
"\usetypescriptfile"?
3b. Specifically, in the case of...
\usetypescript[palatino][ec]
... in which typescript is this defined? (given a vanilla context
minimals installation)
4. What defines the output of "fc-list" or "mtxrun --script fonts
--list"? Do they correspond to files? Type synonyms? etc.
5. Do I need to bother with map files for MKII?
6. Is it particularly recommended that I use MKIV? How stable is it
compared to MKII?

Luigi, what do you mean by "and look into base/*"? Which 'base'? Are
you talking about in the context minimals distribution? some specific
online repository? I have seen the two documents you mentioned.
Re-reading them has clarified things a little bit.

Wolfgang,
Currently the module you linked to
(http://bitbucket.org/wolfs/simplefonts/) is beyond my
understanding... I would first like to understand the mechanism your
module operates on before trying to automate it.

Hans,
I am aware that there are such types of parameters that must be
defined for fonts. I understand 'it is complicated' but this does not
really help make things clearer to me. The inner workings of fonts are
of little concern to me to me at the moment. Right now I do not even
know where to look. I have seen the examples you gave for palatino,
such as...
\usetypescript[palatino][ec]
...but I have no idea where those arguments come from

Thanks.


On 5/13/09, afsmith <adventurecomplete@gmail.com> wrote:
...
> What I would like to do is use the full range of TeX-Gyre fonts (and
> later possibly others) for my existing documents.
> It is not clear to me...
> Whether or not I am using MKIV, nor how to determine which engine I am
> running.
> If not running MKIV/XeTeX, how to determine which fonts are installed.
> What the items from the output of "fc-list" or "mtxrun --script fonts
> --list" correspond to.
> How to use available fonts, nor where to draw valid parameters from
> for use in font commands.
> How to determine what font configurations are available for a given font.
> Whether I need to write typescripts, nor how to find any existing ones.
> Whether I need to concern myself with .map or any other font files.
> Whether I need to configure anything, move any files, etcetera.
> ...As well as anything else I might need to install or use a font
>
> For what it's worth, I have been using the command "texexec" to
> process my tex files, am using a context minimals downloaded about two
> months ago, and am running Linux.
___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2009-05-13 16:31 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 13:18 afsmith
2009-05-13 13:29 ` luigi scarso
2009-05-13 14:36   ` Wolfgang Schuster
2009-05-13 14:48     ` luigi scarso
2009-05-13 15:36       ` Wolfgang Schuster
2009-05-13 15:51         ` luigi scarso
2009-05-13 16:27           ` Wolfgang Schuster
2009-05-14  7:34             ` luigi scarso
2009-05-14  9:11               ` Taco Hoekwater
2009-05-14  9:26                 ` luigi scarso
2009-05-14  9:34                   ` Taco Hoekwater
2009-05-14  9:48                     ` luigi scarso
2009-05-14  9:56                       ` Taco Hoekwater
2009-05-14 10:12                         ` luigi scarso
2009-05-14 10:39                           ` Wolfgang Schuster
2009-05-14 11:21                             ` Arthur Reutenauer
2009-05-14 11:38                               ` Taco Hoekwater
2009-05-14 11:50                                 ` Arthur Reutenauer
2009-05-14 23:48                             ` luigi scarso
2009-05-15  6:18                               ` Wolfgang Schuster
2009-05-14 11:08                           ` Arthur Reutenauer
2009-05-14 12:27                             ` luigi scarso
2009-05-14  9:03             ` luigi scarso
2009-05-14 11:49               ` Khaled Hosny
2009-05-14 12:10                 ` Arthur Reutenauer
2009-05-13 13:32 ` Hans Hagen
2009-05-13 16:31 ` afsmith [this message]
2009-05-13 16:47   ` Hans Hagen
2009-05-13 17:23   ` Wolfgang Schuster
2009-05-13 20:23   ` Aditya Mahajan
2009-05-13 20:31     ` Wolfgang Schuster
2009-05-13 22:12   ` Mohamed Bana

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=5df5befa0905130931u35f777eh102b0ef94c5ec2ea@mail.gmail.com \
    --to=adventurecomplete@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).