ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Vladimir Lomov <lomov.vl@gmail.com>
To: Wolfgang Schuster <schuster.wolfgang@googlemail.com>, ntg-context@ntg.nl
Subject: Re: Computer Modern Unicode fonts
Date: Thu, 30 Sep 2010 22:22:03 +0900	[thread overview]
Message-ID: <20100930132203.GB8731@smoon> (raw)
In-Reply-To: <F8CB25BE-853D-48A6-A88E-ACD2F1AA6E85@gmail.com>

** Wolfgang Schuster [2010-09-30 14:26:24 +0200]:

> 
> Am 30.09.2010 um 14:00 schrieb Hans Hagen:
> 
>> So where is the typeface computer-modern-unicode defined?
>> 
>> Maybe Wolfgang had a another file?
> 
> The typescripts used a tex and a mark file which fails in newer version but i uploaded a new version of them.
> 
> @Vladimir: With the new typescript \setupbodyfont[cmu] is enough to use the font.
Excuse my obtuseness, it is late here, but what/where is 'new typescript'?
In next beta or in hg repo?

Thank you.

P.S. As I understand from Hans example I need to define how serfi/rm
related with computer-modern-unicode. Is it right?

---
WBR, Vladimir Lomov

-- 
I always say beauty is only sin deep.
		-- Saki, "Reginald's Choir Treat"
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2010-09-30 13:22 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 [this message]
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=20100930132203.GB8731@smoon \
    --to=lomov.vl@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=schuster.wolfgang@googlemail.com \
    /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).