ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Jan U. Hasecke" <juh+ntg-context@mailbox.org>
To: ntg-context@ntg.nl
Subject: Re: External fonts handling
Date: Wed, 25 Nov 2015 13:38:25 +0100	[thread overview]
Message-ID: <5655ABC1.3020801@mailbox.org> (raw)
In-Reply-To: <6c85cce34f249e3781ba1a92d0f95819@amu.edu.pl>

In my previous message I wrote that I had the same problem.

I solved it by these steps:

in .bashrc:

export
OSFONTDIR="/usr/local/share/fonts;/usr/share/fonts;$HOME/.fonts;$HOME/.local/share/fonts"


cd $HOME/context

rsync -ptv rsync://contextgarden.net/minimals/setup/first-setup.sh .

./first-setup.sh --modules=all


Note: In contextgarden the last command reads:

sh ./first-setup.sh --modules=all

I guess that my font directory was never read by the install script
because I use bash not sh.

So make sure that your font directories are well exported whatever shell
you use. I am not an expert in this.


A second note:

Ubuntu installs new fonts into the directory

$HOME/.local/share/fonts

Maybe such a hint somewhere in the garden would help.


Ciao!
juh

-- 
Das ZEN von Pandoc
Bücher und E-Books einfach und professionell produzieren
http://www.amazon.de/Das-ZEN-von-Pandoc-professionell/dp/1505218799/
Paperback (232 Seiten) und E-Book
___________________________________________________________________________________
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-11-25 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 11:52 Michał Goliński
2015-11-25 12:04 ` Jan U. Hasecke
2015-11-25 12:38 ` Jan U. Hasecke [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=5655ABC1.3020801@mailbox.org \
    --to=juh+ntg-context@mailbox.org \
    --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).