ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Cc: Yatskovsky <yatskovsky@gmail.com>
Subject: Re: Installing Cyrillic font
Date: Wed, 27 Dec 2006 02:54:36 +0100	[thread overview]
Message-ID: <6faad9f00612261754l3066e0dfq6f181e63c87b3ca0@mail.gmail.com> (raw)
In-Reply-To: <286732239.20061227023101@gmail.com>

On 12/27/06, Vyatcheslav Yatskovsky wrote:
>
> > I might have missed the point completely, but do you set the file
> > encoding anywhere, such as \enableregime[cp1251] (= windows-1251)
> > anywhere? I didn't try your examples, but unless you set this
> > somewhere cyrilic glyphs unlikely to work properly.
>
> Thank you, Mojca.
>
> No, I didn't set the encoding and let me explain why.
>
> When I put \enableregime[cp1251] (I use that very encoding) at the top of my
> script, the output represents transliterated text (all Cyrillic glyphs are
> replaced with corresponding Latin letters). I didn't consider it strange
> until you pointed that to me. Here the .log file of the 'transliterated'

That's "normal". The problems is that you didn't specify the proper
encoding of your font, so TeX doesn't know that your font is cyrillic.

\font\myfirstfont=t2a-n021003l
\myfirstfont

is a plain TeX command, you have to use a ConTeXt command for that.

This is a way to go then:

\starttypescript [map] [timescyr] [t2a]
  \loadmapfile [\typescriptthree-urw-timescyr.map]
\stoptypescript

\starttypescript [serif] [timescyr] [name]
  \definefontsynonym [Serif] [...]
\stoptypescript

\starttypescript [serif] [timescyr] [t2a]
  \definefontsynonym [...] [\typescriptthree-progbot]
[encoding=\typescriptthree]
\stoptypescript

\starttypescript [serif] [t2a]
  \definetypeface [...] [rm] [serif] [timescyr] [default]
[encoding=\typescripttwo]
\stoptypescript

That's only a rought sketch. If you don't get any further using the
existing documentation and wiki, and if nobody else is willing to
help, I can try to complete the definitions if you ask again, but
someone is willing to do that instead ... I won't object.

(Although I suspect that there is a shorter way to tell to TeX which
encoding is being used for a specific font.)

Mojca

  parent reply	other threads:[~2006-12-27  1:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.0.1167056120.20293.ntg-context@ntg.nl>
2006-12-25 14:27 ` Taco Hoekwater
2006-12-26 22:56   ` Vyatcheslav Yatskovsky
2006-12-27  0:06     ` Mojca Miklavec
     [not found]       ` <286732239.20061227023101@gmail.com>
2006-12-27  1:32         ` Fwd: Re[2]: " Vyatcheslav Yatskovsky
2006-12-27  1:33         ` Vyatcheslav Yatskovsky
2006-12-27  1:54         ` Mojca Miklavec [this message]
2006-12-28 23:16 Vyatcheslav Yatskovsky
  -- strict thread matches above, loose matches on Subject: below --
2006-12-28 18:35 Vyatcheslav Yatskovsky
     [not found] <mailman.9628.1166815235.2161.ntg-context@ntg.nl>
2006-12-25  1:20 ` Vyatcheslav Yatskovsky
2006-12-25 11:12   ` Taco Hoekwater

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=6faad9f00612261754l3066e0dfq6f181e63c87b3ca0@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).