ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bugs with minimals 2015.05.24 12:42
Date: Tue, 2 Jun 2015 21:18:07 +0200	[thread overview]
Message-ID: <CALBOmsYT4Uc4E35VxdD7nbptzK=E=aZrzYFYnLfWV9EshB9a6Q@mail.gmail.com> (raw)
In-Reply-To: <20150602.082619.11350.0@webmail10.dca.untd.com>

On Tue, Jun 2, 2015 at 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

If you are using MkII (that is: if you are running "texexec"), you should use
    \enableregime[utf-8]

If you use LuaTeX, there's no need to enable UTF-8. It's already the default.

> (*) Upgrading with "first-setup.sh" deleted all the third-party fonts which we had spent months installing.

I'm sorry to hear that.

The idea is to install fonts to
    texmf-local
or
    texmf-fonts
or
    texmf-project
or somewhere else. But the files get removed from "texmf",
"texmf-context", "texmf-modules" etc.

I'm sorry that that wasn't clear (or maybe not even mentioned) in the
documentation.

> (*) 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)

A "non-beta" version of LuaTeX doesn't exist.

> (*) 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"

The documentation is from 2005 as the URL suggests. So no, it's not
up-to-date. Use LuaTeX instead and you can forget about dirty
workarounds to get the fonts to work.

> (*) 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).

This is all possible (it might require a bit of work to get everything
set up properly), but you should definitely switch to LuaTeX.

Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________

      parent reply	other threads:[~2015-06-02 19:18 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
2016-05-24 10:06   ` Meer, Hans van der
2016-05-24 10:14     ` Mojca Miklavec
2015-06-02 19:18 ` Mojca Miklavec [this message]

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='CALBOmsYT4Uc4E35VxdD7nbptzK=E=aZrzYFYnLfWV9EshB9a6Q@mail.gmail.com' \
    --to=mojca.miklavec.lists@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).