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 16:44:31 +0200 [thread overview]
Message-ID: <51b0095d0906040744o29f50c02q8fdffbfc43bf0952@mail.gmail.com> (raw)
In-Reply-To: <51b0095d0906040700w3ec10cdcocabd0bf9703db5e0@mail.gmail.com>
Wow. Now, I'm lost -- and i still can't make it work anyway.
Could you explain right from the start ?
Let's assume (as it is the case on my system) that the Delicious fonts
are properly installed *and* the font database knows about it.
Let's assume context = LuaTeX mkiv
Now,
1. if I want to create a typescript file supporting some XX fonts, do
I need to name the file type-XX.some_extension, or is it only a
convention and the file could also be named XX.some_extension or even
whatever.some_extension ?
2. what should be the extension for mkiv ? .mkiv ? .tex ? Are both allowed ?
3. Assuming I properly install such
http://bitbucket.org/wolfs/typescripts/src/7050bb6918bb/type-exljbris.mkiv
file, should I load it using
\usetypescriptfile[type-exljbris]
or
\usetypescriptfile[exljbris]
?
4. What is the relationship between type-exljbris.mkiv and
type-exljbris.tex ? Is type-exljbris.tex necessary when using mkiv ?
5. In order to install one or several typescript files, I should first
copy them, either in
tex/texmf-fonts/tex/context/user
or in
tex/texmf-project/tex/context/user
right ?
But then,
what is it necessary to run ?
- context --generate ?
- mtxrun --script fonts --reload ?
- both ?
6. How comes ConTeXt can silently substitute my fonts, without even
outputting any error message ?
How to change this behaviour ?
How to disable font substitution ?
Hopefully you forgive me for asking so many questions. Beware, answers
will be recorded and published in the wiki ;-)
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-06-04 14:44 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
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 [this message]
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=51b0095d0906040744o29f50c02q8fdffbfc43bf0952@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).