ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Nicolas Girard <nicolas.girard@nerim.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Where to store typescripts ?
Date: Thu, 4 Jun 2009 11:11:19 +0200	[thread overview]
Message-ID: <51b0095d0906040211w7e7ecf10rd02d2c52f2646240@mail.gmail.com> (raw)
In-Reply-To: <fe8d59da0906040138t5b873869gb71f0ff5f10cbae@mail.gmail.com>

2009/6/4 luigi scarso <luigi.scarso@gmail.com>:
>
>
> On Thu, Jun 4, 2009 at 10:34 AM, Nicolas Girard <nicolas.girard@nerim.net>
> wrote:
>>
>> Hi,
>>
>> Where should typescript files be stored ?
>
> If you have minimals(-beta)
> try
> minimals/tex/texmf-context/tex/context/user
>

Hi Luigi,
thanks for your answer.
I'm using the latest mkiv installed over texlive 2008.
It is a system directory ; is it the only one ?

Anyway I couldn't get my typescript file to work.
Here's what I did:

(assume TF is http://bitbucket.org/wolfs/typescripts/src/7050bb6918bb/type-exljbris.mkiv
)

1. put the contents of TF in a test document along with
\usetypescript[delicious]
The document compiled fine and the Delicious fonts were properly included.

2. copied TF in tex/context/user/ as adviced
3. ran mktexlsr, just in case
4. In the test document, removed the contents of TF and replaced it with
\usetypescriptfile[type-exljibris]

The compilation ran smoothly, I should say too smoothly, because I
couldn't find any font-related error message, neither in the output,
nor in the log file. And however, ConTeXt used lmodern fonts instead
of the Delicious fonts.

Cheers,
Nicolas
___________________________________________________________________________________
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-06-04  9:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04  8:34 Nicolas Girard
2009-06-04  8:38 ` luigi scarso
2009-06-04  9:05   ` Hans Hagen
2009-06-04  9:11   ` Nicolas Girard [this message]
2009-06-04  9:21     ` luigi scarso
2009-06-04 14:00       ` Nicolas Girard
2009-06-04 14:06         ` luigi scarso
2009-06-04 14:07         ` Wolfgang Schuster
2009-06-04 14:21           ` luigi scarso
2009-06-04 14:11         ` Peter Rolf
2009-06-04 14:44         ` Nicolas Girard
2009-06-04 14:54           ` luigi scarso
2009-06-04 15:28             ` Nicolas Girard
2009-06-04 15:33               ` luigi scarso
2009-06-04 17:18                 ` Nicolas Girard
2009-06-04 15:55               ` Wolfgang Schuster
2009-06-08 22:35             ` Mojca Miklavec
2009-06-09  9:47               ` Nicolas Girard
2009-06-04 17:17           ` Wolfgang Schuster
2009-06-04 17:29             ` Nicolas Girard

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=51b0095d0906040211w7e7ecf10rd02d2c52f2646240@mail.gmail.com \
    --to=nicolas.girard@nerim.net \
    --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).