ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Olya Briginets <bolya@ukrpost.net>
Subject: How about Cyrillic?
Date: Sun, 05 Aug 2001 11:15:46 +0300	[thread overview]
Message-ID: <3B6D00B2.697C4154@ukrpost.net> (raw)

Hello,

  Is cyrillic support planned in ConTeXt? 
  Is there any cyrillization available?

  I have made some support for cyrillic languages (only russian and
ukrainian so far) and it works for me, however, I'm not sure I have made it
ideologically correct, do not know the right way to do it. I use officially
supported in LaTeX (babel uses it) T2A font encoding, and windows cyrillic
input encoding (cp1251).

  Some problems with cyrillic are that there are several input encoding in
use -- koi-8 in *nix world, Windows cp1251 in Windows world and DOS cp866 in
DOS (and Windows too) world (not to mention ISO cyrillic, which in fact are
rarely used, and Mac cyrillic encoding, as Mac users, I believe, use
commercial out-of-box soft so I have not care about them).
And the only supported as freeware font encodings, T2*, differ from all the
above mentioned input encodings.
  In LaTeX, this situation is handled via inputenc/fontenc mechanism;
inputenc is not very good because it makes lot of letters active. I use
\defineactivecharacter in my ConTeXt cyrillization. This, however, excludes
the possibility of cyrillic interface.

  Does one know how to handle this?

(The other possibility would by to create virtual fonts for each encoding,
but there would be too many of them, and, besides, I know nothing about
virtual fonts creation.)

Olya


             reply	other threads:[~2001-08-05  8:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-05  8:15 Olya Briginets [this message]
2001-08-06  7:54 ` 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=3B6D00B2.697C4154@ukrpost.net \
    --to=bolya@ukrpost.net \
    /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).