From: Philipp Reichmuth <reichmuth@web.de>
Subject: Re: XeTeX and built-in glyph generation
Date: Thu, 02 Nov 2006 12:15:24 +0100 [thread overview]
Message-ID: <eick0c$nnb$1@sea.gmane.org> (raw)
In-Reply-To: <4549CCFE.50105@wxs.nl>
Hans Hagen schrieb:
> Philipp Reichmuth wrote:
>> - character[ range]s which get passed directly to the underlying engine
>> (useful mainly with XeTeX and possibly with Aleph/Omega)
>> - character[ range]s which get constructed from accents
>> - character[ range]s which get used from a different typescript; for
>> example if I have passages or quotations in a script which isn't
>> available in my typescript, it would be nice to say that "all
>> IPA/Greek/Old Church Slavonic" should come from a substitution
>> typescript where these scripts are available and look good.
>
> we're going to built that kind of logic (and a bit more) into luatex / context mkiv ; after that we can see to what extend we can support the xetex way as well
>
> after tug 2006 we enter the font part pf the luatex/orientaltex project
OK. Sounds great. If you need a tester, I'll be more than happy to
provide lots of awkward cases and sift through them.
In the meantime, is it possible to enable/disable ConTeXt's UTF-8
handler selectively for pieces of text? such as:
\starttext
\enableregime[utf]
- some Unicode text processed by CoNTeXt for diacritics etc. -
\disableregime[utf]
- some Unicode text in some other script processed natively by XeTeX -
\stoptext
That would do the job in the meantime.
Philipp
next prev parent reply other threads:[~2006-11-02 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 10:04 Philipp Reichmuth
2006-11-02 10:48 ` Hans Hagen
2006-11-02 11:15 ` Philipp Reichmuth [this message]
2006-11-02 11:50 ` Philipp Reichmuth
2006-11-02 11:57 ` Hans Hagen
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='eick0c$nnb$1@sea.gmane.org' \
--to=reichmuth@web.de \
--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).