ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Bugs with minimals 2015.05.24 12:42
Date: Tue, 02 Jun 2015 14:51:54 +0200	[thread overview]
Message-ID: <556DA6EA.8090402@wxs.nl> (raw)
In-Reply-To: <20150602.082619.11350.0@webmail10.dca.untd.com>

On 6/2/2015 2:26 PM, david.boerschlein@juno.com wrote:
>
> (*) tex error       > error on line 1 in file /var/www/vhosts/door43.org/tools/nototest.tex: ! Undefined control sequence
>      l.1 \useregime
>              [utf]
>      1 >>  \useregime[utf]
>      2     \enableregime[utf]
>      Version: 2015.05.24 12:42
>
> (*) Upgrading with "first-setup.sh" deleted all the third-party fonts which we had spent months installing.

If you install extra fonts and files, you should put them in

tex/texmf-fonts
tex/texmf-project

as these are left untouched. That has always been the recommendation. 
The other trees will be synchronized in an update and that also includes 
deleting obsolete files.

> (*) Installing the "context=current" installed a "beta" version of luatex:
>      context --version
>      mtx-context     | current version: 2015.05.24 12:42
>      luatex --version
>      This is LuaTeX, Version beta-0.80.0 (TeX Live 2015) (rev 5238)
>
> (*) http://tug.org/pracjourn/2005-2/schmitz/schmitz.pdf (none of the commands texfont, ttf2afm, updmap, come with the latest ConTeXt minimals 2015.05.24 12:42) [Is this really the up-to-date documentation on how to install a true-type font?]    It does not seem to discuss what to do if all we have is an ".otf" but no ".ttf"
>
> (*) Documentation request: typescripts for "ttf" and "otf" files which may or may not have bold, italics, etc with fallback-families and Unicode ranges and separate files for Unicode-ranges (e.g., Google Noto fonts).

you can put the fonts in

tex/texmf-fonts/fonts/data/someplace

and run

mtxrun --generate

and then try the selectfont command

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2015-06-02 12:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02 12:26 david.boerschlein
2015-06-02 12:51 ` Hans Hagen [this message]
2016-05-24 10:06   ` Meer, Hans van der
2016-05-24 10:14     ` Mojca Miklavec
2015-06-02 19:18 ` 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=556DA6EA.8090402@wxs.nl \
    --to=pragma@wxs.nl \
    --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).