ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Diego Depaoli" <trebestie@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Losing my patience with (understanding) ConTeXt/LuaTeX's font handling... [ re: Whacko font behaviour ? ( Or Am I ? :O) ]
Date: Fri, 18 Jul 2008 23:22:09 +0200	[thread overview]
Message-ID: <83e5fb980807181422n107a8151xc747e2765d9c44cc@mail.gmail.com> (raw)
In-Reply-To: <115224fb0807180816s1c045c37hd621e343d8fd34bd@mail.gmail.com>

2008/7/18 Wolfgang Schuster <schuster.wolfgang@googlemail.com>:
>> but this issue still exists in Ubuntu with such fonts imported from Windows.
>> Where mtxrun catches fonts filenames?
>
> Hi Diego,
Hello Wolfgang,
>
> we are talking about two differents things, what you mean is the filename
> of the fonts you could access with [file:...] in typescripts and which is
> different on Windows (and all other where the core font packages are used)
> and on Mac. The font name is another thing and can be different from the
> file name, you could access fonts by font name with [name:...] in MkIV and
> this name should (not sure if this is so) be the same on both systems.

That's clear to me, but my question was about the wrong correspondence
between font names and filename.
As I wrote mtxrun --script fonts --lists showed filenames which I
didn't find anywhere, so I thought mtxrun rewrote them.
Repeating the same procedure under FreeBSD all goes right.
Perhaps in my Ubuntu system there is more than one Times New Roman,
Arial..., (even I don't know where they live) and this confused
ConTeXt.
Next time I boot Ubuntu, I'll search in the whole filesystem.
Thanks for the answer and sorry for the noise.

-- 
Diego Depaoli
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2008-07-18 21:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16 19:18 Alan Stone
2008-07-16 23:14 ` Diego Depaoli
2008-07-16 23:23   ` Diego Depaoli
2008-07-17  6:30   ` Wolfgang Schuster
2008-07-17 15:39     ` Diego Depaoli
2008-07-18 15:16       ` Wolfgang Schuster
2008-07-18 21:22         ` Diego Depaoli [this message]
2008-07-19  4:49           ` Charles P. Schaum
2008-07-19 10:03             ` Alan Stone
2008-07-19 13:25               ` John Culleton
2008-07-21  6:38                 ` Wolfgang Schuster
2008-07-17  6:43 ` Wolfgang Schuster
2008-07-17 15:00   ` Alan Stone
2008-07-18 15:12     ` Wolfgang Schuster
2008-07-18 15:56       ` Olivier Guéry
2008-07-18 20:45       ` Alan Stone
2008-07-18 21:44         ` Andrea Valle
2008-07-17 11:32 ` Wolfgang Schuster
2008-07-20 11:13 Alan Stone
2008-07-21  6:29 ` Wolfgang Schuster
2008-07-21  7:26   ` Alan Stone

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=83e5fb980807181422n107a8151xc747e2765d9c44cc@mail.gmail.com \
    --to=trebestie@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).