From: Mikael Persson <mickep@gmail.com>
Subject: Re: Re: Russian
Date: Wed, 13 Apr 2005 17:59:37 +0200 [thread overview]
Message-ID: <d5fddde005041308591a78e1f7@mail.gmail.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0504131659060.19448@persius.rz.uni-potsdam.de>
[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]
On 4/13/05, Albrecht Kauffmann <alkauffm@rz.uni-potsdam.de> wrote:
>
>
> On Wed, 13 Apr 2005, Albrecht Kauffmann wrote:
>
> > Hi all,
> >
> > I've tried to typeset in Russian with utf-8 fonts, like explained at
> > contextgarden.net/Russian. cm-super-fonts are installed, included tfm-,
> > enc- and map-files. Running the example
> >
> > \enableregime[utf]
> > \useencoding[cyr]
> >
> > \definetypeface [russian]
> > [rm] [serif] [computer-modern] [default] [encoding=t2a]
> >
> > \setupbodyfont[russian]
> > \starttext
> > ???? ? ???? % Some Russian characters
> > \stoptext
> >
> > I got error messages (see the attached logfile): the font larm1000 was not
> > found.
> >
> > Have I to edit some lines in type-map.tex? Or what could be wrong?
>
> If I add to type-map.tex:
> \starttypescript [map] [computer-modern] [t2a]
> \loadmapfile[cm-super-t2a.map]
> \stoptypescript
>
> I get russian fonts, but these are not the right ones.
>
> I would be very glad, if anyone could help me to solve the problem.
>
> Thanks
> Albrecht
>
>
Hello Albrecht,
Are you sure that you have saved your file in the utf-8 encoding and
not in koi8r or something? The problem of getting the wrong characters
can come from that. Moreover, the example:
%%%%%%%%%%%%%%%%%%
\enableregime[utf]
\useencoding[cyr]
\definetypeface [russian]
[rm] [serif] [computer-modern] [default] [encoding=t2a]
\setupbodyfont[russian]
\starttext
Мама и Папа % Some Russian characters
\stoptext
%%%%%%%%%%%%%%%%%%
from the wiki page works here. (Ok, since I wrote the page it would be
kind of weird if it did not). Have you generated the tmf files?
Have anyone else tried if it works for them?
Regards, Micke P
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2005-04-13 15:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 1:50 border widths with TABLE Paul Tremblay
2005-04-12 11:05 ` Eckhart Guthöhrlein
2005-04-12 19:54 ` Paul Tremblay
2005-04-12 20:20 ` Hans Hagen
2005-04-12 20:35 ` Henning Hraban Ramm
2005-04-12 21:01 ` Hans Hagen
2005-04-12 20:49 ` Hans Hagen
2005-04-13 1:25 ` Paul Tremblay
2005-04-13 8:17 ` Eckhart Guthöhrlein
2005-04-13 9:44 ` Russian Albrecht Kauffmann
2005-04-13 15:03 ` Russian Albrecht Kauffmann
2005-04-13 15:59 ` Mikael Persson [this message]
2005-04-14 8:04 ` Russian Albrecht Kauffmann
2005-04-14 8:57 ` Mikael Persson
2005-04-14 12:00 ` mswintex.zip Lutz Haseloff
2005-04-14 12:44 ` AW: mswintex.zip Michael Fuchs
2005-04-14 12:51 ` mswintex.zip Patrick Gundlach
2005-04-14 13:44 ` mswintex.zip Lutz Haseloff
2005-04-14 18:43 ` Willi Egger
2005-04-14 19:16 ` mswintex.zip Patrick Gundlach
2005-04-14 19:26 ` mswintex.zip 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=d5fddde005041308591a78e1f7@mail.gmail.com \
--to=mickep@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).