From: Vladimir Lomov <lomov.vl@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Computer Modern Unicode fonts
Date: Thu, 30 Sep 2010 18:36:14 +0900 [thread overview]
Message-ID: <AANLkTin4Hv6_9cvF_XARidLF3YBr5c50j8HD4RZjHOyE@mail.gmail.com> (raw)
In-Reply-To: <4CA4522B.6080805@wxs.nl>
Hi.
2010/9/30 Hans Hagen <pragma@wxs.nl>:
> If these are the huge traced cm supers I'd rather not have them in the
> minimals but as extra as they consume a log of space.
No, it's otf fonts. For reference you could see this branch:
http://www.ctan.org/tex-archive/fonts/cm-unicode/fonts/otf/
> If it's just cyrillic .. maybe it's more interesting to use fallbacks, given
> that we have a cyrillic only variant available for that (there are type ones
> as we have support for the t2* encodings in mkii).
It's not the only way to get Cyrillic as any other language in ConTeXt.
> Btw, one of the reasons why lm/gyre have no cyrillic (or had cyrilic
> removed) is that in spit of all efforts to locate people, no one is willing
> to check them and do some quality control. It has been discussed before: if
> there is a group of volunteers the glyphs might show up again in the fonts.
If I not mistake part of work in cm-super was done by Vladimir
Volovich (or whole work?).
So, I should ask Wolfgang Schuster (author of type-cmu.mkiv) what
could be wrong with the document? May be I do completely wrong with
that typescript?
Khaled Hosny == KH:
KH>You actually need `mtxrun -script fonts --reload` to update font database.
I tried. Without success.
---
WBR, Vladimir Lomov
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2010-09-30 9:36 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
2010-09-30 11:43 ` Vladimir Lomov
2010-09-30 9:02 ` Hans Hagen
2010-09-30 9:36 ` Vladimir Lomov [this message]
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=AANLkTin4Hv6_9cvF_XARidLF3YBr5c50j8HD4RZjHOyE@mail.gmail.com \
--to=lomov.vl@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).