ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Khaled Hosny <khaledhosny@eglug.org>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Computer Modern Unicode fonts
Date: Thu, 30 Sep 2010 14:24:58 +0300	[thread overview]
Message-ID: <20100930112458.GA7061@khaled-laptop> (raw)
In-Reply-To: <4CA45C2B.4020607@wxs.nl>

On Thu, Sep 30, 2010 at 11:45:15AM +0200, Hans Hagen wrote:
> On 30-9-2010 11:18, Khaled Hosny wrote:
> >On Thu, Sep 30, 2010 at 06:00:37PM +0900, Vladimir Lomov wrote:
> >>Hi.
> >>
> >>VL>  Not sure about how 'context --generate'' works but I didn't that. May
> >>VL>  be it doesn't like links?
> >>
> >>I meant that I ran (several times) 'context --generate' after I made a
> >>link to cm-unicode.
> >
> >You actually need `mtxrun -script fonts --reload` to update font
> >database.
> 
> the database is not needed when filenames are used

But type-cmu.mkiv is loading fonts by name: not file:

-- 
 Khaled Hosny
 Arabic localiser and member of Arabeyes.org team
 Free font developer
___________________________________________________________________________________
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:[~2010-09-30 11:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30  8:05 Vladimir Lomov
2010-09-30  8:14 ` Willi Egger
2010-09-30  8:34 ` Hans Hagen
2010-09-30  8:40   ` Khaled Hosny
2010-09-30  9:00     ` Vladimir Lomov
2010-09-30  9:18       ` Khaled Hosny
2010-09-30  9:45         ` Hans Hagen
2010-09-30 11:09           ` Vladimir Lomov
2010-09-30 11:12             ` Hans Hagen
2010-09-30 11:18               ` Vladimir Lomov
2010-09-30 12:00                 ` Hans Hagen
2010-09-30 12:26                   ` Wolfgang Schuster
2010-09-30 13:22                     ` Vladimir Lomov
2010-09-30 13:46                       ` Wolfgang Schuster
2010-10-01  2:50                         ` Vladimir Lomov
2010-10-01  3:03                           ` Mojca Miklavec
2010-10-01  3:53                             ` Vladimir Lomov
2010-10-01 11:29                               ` Mojca Miklavec
2010-09-30 14:10                       ` Hans Hagen
2010-09-30 13:14                   ` Vladimir Lomov
2010-09-30 12:20                 ` Hans Hagen
2010-09-30 13:37                   ` Vladimir Lomov
2010-09-30 14:12                     ` Hans Hagen
2010-10-01  2:44                       ` Vladimir Lomov
2010-10-01  4:05                   ` Vladimir Lomov
2010-09-30 11:24           ` Khaled Hosny [this message]
2010-09-30 11:43             ` Vladimir Lomov
2010-09-30  9:02     ` Hans Hagen
2010-09-30  9:36       ` Vladimir Lomov

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=20100930112458.GA7061@khaled-laptop \
    --to=khaledhosny@eglug.org \
    --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).