From: Henning Hraban Ramm <hraban@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: analyzing type-otf.tex
Date: Tue, 8 Apr 2008 22:30:21 +0200 [thread overview]
Message-ID: <0E155E39-E3BB-42B4-AAF4-E1911B9C015C@fiee.net> (raw)
In-Reply-To: <47FB59DD.1080909@wxs.nl>
Am 2008-04-08 um 13:41 schrieb Hans Hagen:
>>
>> To Hraban: oh, I did not understand you joke at first :-) Now I see
>> what you were trying to say with "extending the font to the full
>> unicode range" :-) And sure enough - LuaTeX doesn't do that either.
Sorry, I should know since a few years that my jokes aren't
understandable... ;-)
(I tend to joke with my father about details of grammar and
constantly quote lyrics of unknown songs...)
> at some point we can start thinking of defining virtual font
> collections
Would be cool!
I'm working occasionally on a songbook that contains a Russian song,
and I'd like to print the original text in cyrillic (even if I can
hardly read it).
I've everything in UTF-8, so it would be great if ConTeXt could
change the font automatically or language-dependent.
I still didn't try anything with that, though, maybe it's easy - the
base font is Century Schoolbook (because that's LilyPond's default
font and it works well for a songbook), and if I use XeTeX/luaTeX
with TeXGyre Schola, it should just work. (Or don't you think?)
Ok, maybe I don't even need virtual font collections...
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2008-04-08 20:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 11:35 Henning Hraban Ramm
2008-04-06 12:37 ` Henning Hraban Ramm
2008-04-07 10:58 ` Mojca Miklavec
2008-04-07 18:22 ` Henning Hraban Ramm
2008-04-07 22:43 ` Mojca Miklavec
2008-04-07 22:50 ` Mojca Miklavec
2008-04-08 6:44 ` Wolfgang Schuster
2008-04-08 7:11 ` Henning Hraban Ramm
2008-04-08 7:25 ` Wolfgang Schuster
2008-04-08 7:53 ` Hans Hagen
2008-04-08 8:13 ` Hans Hagen
2008-04-08 10:39 ` Mojca Miklavec
2008-04-08 11:41 ` Hans Hagen
2008-04-08 20:30 ` Henning Hraban Ramm [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=0E155E39-E3BB-42B4-AAF4-E1911B9C015C@fiee.net \
--to=hraban@fiee.net \
--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).