From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Computer Modern Unicode fonts
Date: Thu, 30 Sep 2010 13:12:49 +0200 [thread overview]
Message-ID: <4CA470B1.2070708@wxs.nl> (raw)
In-Reply-To: <AANLkTik8a9qFCJSMf6XuwUCj+ribzs2xyR--mgJGvSmo@mail.gmail.com>
On 30-9-2010 1:09, Vladimir Lomov wrote:
> Hi.
> 2010/9/30 Hans Hagen<pragma@wxs.nl>:
>> 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
> Ok. Suppose that I place in currect directory the file 'type-cmu.mkiv'
> (attached, sorry Wolfgang, I don't mention in the file that I changed
> it, I need it for test only) and run as usual
> $ context ex_ru.tex
> (and I also change '\usetypescriptfile' to '\usetypefile' because then
> I see in terminal output that local 'type-cmu.mkiv' is used) but again
> I don't get CM-U fonts.
how does your test file look
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-09-30 11:12 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 [this message]
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
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=4CA470B1.2070708@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).