From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Subject: Re: unic-xxx.tex glyph lists: minor bugs, questions
Date: Thu, 9 Nov 2006 17:56:43 +0100 [thread overview]
Message-ID: <6faad9f00611090856j55b19436o69f8ef1d606c984f@mail.gmail.com> (raw)
In-Reply-To: <6faad9f00611090851wc33a00bg34347cf4fc12eb69@mail.gmail.com>
> > > The best way out would be if I could enable ConTeXt's UTF-8 regime while
> > > running XeTeX in \XeTeXinputencoding=bytes mode, but I haven't gotten
> > > that to work yet.
That would mean that you loose the whole range of glyphs & scripts
outside of the scope which ConTeXt supports (you would land almost at
the level of pdfTeX again). For most european users that might still
be something reasonable, but I wouldn't go that way.
> > maybe mojca has
(little correction to what I wrote in my previous mail)
If you were really looking for that part of code - simply replace
\expandafter \endinput inside XETEX block in regi-utf.tex with
\XeTeXinputencoding=bytes. Then \enableregime[utf-8] will mean that
ConTeXt took control over utf instead of XeTeX. From what I understood
on the wiki, it probably used to be that way at the beginning, but
then Hans changed his mind and decided to ignore \enableregime[utf]
completely when processing with XeTeX.
Mojca
next prev parent reply other threads:[~2006-11-09 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 1:24 Philipp Reichmuth
2006-11-05 14:27 ` Hans Hagen
2006-11-06 22:56 ` Philipp Reichmuth
2006-11-09 16:51 ` Mojca Miklavec
2006-11-09 16:56 ` Mojca Miklavec [this message]
2006-11-14 11:35 ` Hans Hagen
2006-11-14 11:42 ` Hans Hagen
2006-11-16 10:49 ` Philipp Reichmuth
2006-11-16 13:12 ` Sanjoy Mahajan
2006-11-16 16:20 ` Hans Hagen
2006-11-22 23:54 ` Sanjoy Mahajan
2006-11-23 9:56 ` 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=6faad9f00611090856j55b19436o69f8ef1d606c984f@mail.gmail.com \
--to=mojca.miklavec.lists@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).