From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: Yatskovsky <yatskovsky@gmail.com>,
"mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Can I use OpenType fonts with ConTeXt on Windows right now
Date: Fri, 13 Apr 2007 21:07:46 +0200 [thread overview]
Message-ID: <6faad9f00704131207i1da38a28mb3eb8129b6336693@mail.gmail.com> (raw)
In-Reply-To: <1897999158.20070413192920@gmail.com>
I admit it. I admit everything. I'm the guily one for the whole mess
about XeTeX!
http://wiki.contextgarden.net/Encodings_and_Regimes_in_XeTeX
Some time ago Hans has decided to ignore \enableregime in XeTeX. I
could have written more (and cite things), but I'm in a hurry right
now and I will probably be offline for the whole weekend.
The wiki pages need a massive adaption! Really.
On 4/13/07, Vyatcheslav Yatskovsky <yatskovsky@gmail.com> wrote:
> Hello Mojca,
>
> And what is more, you have said that other input regimes should work as well, but the following fragment doesn't work. (arbitrary symbols are substituted)
I said that it could have worked ... I didn't say that it actually works ;)
\enableregime should be adapted in my opinion. I had a patch already,
but I don't have time to look for it right now. The following should
work though:
Either
\XeTeXinputencoding "bytes"
% uncomment the line which prevents loading of regimes in XeTeX
\enableregime[cp1251]
or
\XeTeXinputencoding "cp1251"
> \enableregime[cp1251]
> \definetypeface[myface][rm][Xserif][Times New Roman]
> \setupbodyfont[myface, 12pt]
> \starttext
> Hello World!
> Привет!
> \stoptext
>
> (I really saved the file in that encoding - Windows Cyrillic, 1251)
>
> It is quite disappointing, because that encoding would cover my English-Russian-Ukrainian typesetting needs fully. UTF is amazing but not as convenient as cp1251.
There should really be no problem in adapting the \enableregime to
cover those regimes (it's really a simple patch). From the fact that
Hans added quite some new files and definitions during transition to
luaTeX ... I guess that he might still be willing to adapt that
behaviour in XeTeX as well.
Mojca
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2007-04-13 19:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 13:26 Vyatcheslav Yatskovsky
2007-04-13 13:40 ` Mojca Miklavec
2007-04-13 13:56 ` Vyatcheslav Yatskovsky
[not found] ` <6faad9f00704130735q60d1c0aci3a120f559770d90a@mail.gmail.com>
[not found] ` <1897999158.20070413192920@gmail.com>
2007-04-13 19:07 ` Mojca Miklavec [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-12 20:05 Paul Schalck
[not found] <mailman.4826.1176378848.17432.ntg-context@ntg.nl>
2007-04-12 17:32 ` Vyatcheslav Yatskovsky
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=6faad9f00704131207i1da38a28mb3eb8129b6336693@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=yatskovsky@gmail.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).