From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with Xetex
Date: Sun, 15 Jun 2008 22:50:35 +0200 [thread overview]
Message-ID: <4855809B.3080500@wxs.nl> (raw)
In-Reply-To: <20080615213013.tmgaqh468k4ksg40@w13.mail.sapo.pt>
cidadaum@sapo.pt wrote:
> Probably I am the most troubled, unsuccessful beginner in this list
> (it's my <i>fado</i>), anyway:
> I have two installations of context: one in ~/texmf; another in
> ~/context to which I switch typing . ~/context/tex/setuptex
> ~/context/tex.
> The first one has a problem with 8bit output (\enableregiem[utf8]: it
> says in the log file: possible problem with 8bit output.
> Xetex hangs on with: kpathsea mktextfm lmroman...
> The second installation has another problem with xetex: "could not
> open config file dvipdfmx.cfg"
maybe the first tree has an ancient xetex and/or context and/or those
fonts ... xetex is a moving target and when possible context adapts to
it and as a result they need to be in sync (the same is true for context
mkiv and luatex)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-06-15 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 20:30 cidadaum
2008-06-15 20:50 ` Hans Hagen [this message]
2008-06-15 21:45 ` 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=4855809B.3080500@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).