From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: fonts with luatex
Date: Thu, 10 Jul 2008 16:05:30 +0200 [thread overview]
Message-ID: <6faad9f00807100705s25e7f970l3667bffd40048f13@mail.gmail.com> (raw)
In-Reply-To: <83e5fb980807100650n35e25d21i6c140229cbc99ce0@mail.gmail.com>
On Thu, Jul 10, 2008 at 3:50 PM, Diego Depaoli wrote:
> 2008/7/10 Mojca Miklavec <mojca.miklavec.lists@gmail.com>:
>> I have texmf tree on vfat partition (same disk, another partition
>> shared with windows that I never use :), and it works without
>> problems. What/when exactly does it fail?
> strange, I sent a mail noticing this issue, but seems never became...
> ----------
> Minimals is installed in my $HOME
> File to build is located in a partition (/media/disk) shared between
> ubuntu and FreeBSD
> Now I'm on ubuntu
> from my $HOME texexec --xtx /media/disk/file.tex works
> from /media/disk texexec --xtx file.tex fails with
> ! Font \*fontin12ptsstfss*:=Fontin_Sans_R_45b:+liga;+kern;mapping=tlig;+trep; a
> t 12.0pt not loadable: Metric (TFM) file or installed font not found.
> texexec --lua works when launched from both locations.
> Something is broken in fonts path detection?
Where do you have that font (Fontin_Sans_R_45b)?
Another observation for Hans: +trep should not reach XeTeX.
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-07-10 14:05 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 14:00 Alan Stone
2008-07-08 15:02 ` Hans Hagen
2008-07-08 18:23 ` Alan Stone
2008-07-09 8:16 ` Hans Hagen
2008-07-09 8:24 ` Alan Stone
2008-07-09 8:40 ` Hans Hagen
2008-07-09 10:03 ` Alan Stone
2008-07-09 11:19 ` Alan Stone
2008-07-09 11:42 ` Hans Hagen
2008-07-09 14:15 ` Arthur Reutenauer
2008-07-09 14:25 ` Alan Stone
2008-07-09 15:04 ` Arthur Reutenauer
2008-07-09 15:13 ` Taco Hoekwater
2008-07-09 15:18 ` Arthur Reutenauer
2008-07-09 17:00 ` Alan Stone
2008-07-09 18:26 ` Alan Stone
2008-07-10 6:21 ` Hans Hagen
2008-07-10 6:54 ` Alan Stone
2008-07-10 6:47 ` Hans Hagen
2008-07-10 7:15 ` Alan Stone
2008-07-10 7:21 ` Wolfgang Schuster
2008-07-10 7:45 ` Alan Stone
2008-07-10 7:25 ` Mojca Miklavec
2008-07-10 8:12 ` Alan Stone
2008-07-10 8:52 ` Wolfgang Schuster
2008-07-10 9:00 ` Alan Stone
2008-07-10 8:55 ` Alan Stone
2008-07-10 9:13 ` Alan Stone
2008-07-10 9:36 ` Alan Stone
2008-07-10 9:49 ` Mojca Miklavec
2008-07-10 10:02 ` Alan Stone
2008-07-10 9:52 ` Mojca Miklavec
2008-07-10 11:39 ` Diego Depaoli
2008-07-10 12:16 ` Mojca Miklavec
2008-07-10 13:50 ` Diego Depaoli
2008-07-10 14:05 ` Mojca Miklavec [this message]
2008-07-10 14:38 ` Diego Depaoli
2008-07-10 8:14 ` Hans Hagen
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=6faad9f00807100705s25e7f970l3667bffd40048f13@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).