ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Radhelorn <radhelorn@mail.ru>
Subject: Re: Basic question on Unicode and ConTeXt
Date: Fri, 15 Jul 2005 09:16:46 +0400	[thread overview]
Message-ID: <42D746BE.3010101@mail.ru> (raw)
In-Reply-To: <1121368405.42d6b9557eabf@www.domainfactory-webmail.de>

Steffen Wolfrum wrote:
>>>I know there is \enableregime[utf]
>>>but what else I needed that the output equals my utf-8 input?
>>>
>>>Could some maybe give a short and usable How-To on common examples:
>>>Greek
>>>Russian
>>>an East European language
>>>and an Asian language?
>>
>>You did read http://contextgarden.net/Encodings_and_Regimes and
>>linked pages, did you?
>>If you learn anything new, please add it to the wiki!
> 
> Well, yes, I wasn't interested in e.g. VISCII, but I read the info for UTF.
> But as you wrote "linked pages" I became more curious and looked up also those
> pages. Indeed, there is more:
> 
> But, why is the Vietnamese example with
> \enableregime[utf]
> \setupencoding[default=t5
> linked under
> vis = viscii	VISCII	Vietnamesevis = viscii	VISCII	Vietnamese
> and not accessable with
> utf	UTF-8	Unicode ? (Same for cyrillic)
> 
> Is this just a wrong link, or does this show that I don't have understood the
> realationship between regimes and encoding?
> 
> Shouldn't all UTF relevant examples be listed under UTF?
> 
> 

\enableregime is not enough. You need to setup font encoding and 
appropriate bodyfont. For these see type-enc, type-pre and such.

Example for cyrillic:

\enableregime [utf]
\setupencoding [default=t2a]
\usetypescript [modern-base] [\defaultencoding]
\setupbodyfont [modern]

\starttext
Тест.
\stoptext


-- 
Radhelorn <radhelorn@mail.ru>

  parent reply	other threads:[~2005-07-15  5:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14  9:30 Steffen Wolfrum
2005-07-14 10:29 ` Henning Hraban Ramm
2005-07-14 19:13   ` Steffen Wolfrum
2005-07-14 19:32     ` VnPenguin
2005-07-15  5:16     ` Radhelorn [this message]
2005-07-15  9:09     ` Henning Hraban Ramm
2005-07-15 18:43   ` Mojca Miklavec
2005-07-15 18:59     ` hungarumlaut (was: Basic question on Unicode) Henning Hraban Ramm
2005-07-15 21:13     ` ISO/windows encodings (was: Basic question on Unicode ...) Mojca Miklavec
2005-07-17 23:38       ` ISO/windows encodings Hans Hagen
2005-07-17 20:01     ` Basic question on Unicode and ConTeXt Hans Hagen
2005-07-18  5:50       ` VnPenguin
2005-07-18 20:26       ` Mojca Miklavec
2005-07-18 21:46         ` Hans Hagen
2005-07-18 21:54         ` Hans Hagen
2005-07-18 23:11           ` Mojca Miklavec
2005-07-19  8:06             ` Hans Hagen
2005-07-20 20:35               ` Christopher Creutzig
2005-07-21  0:52                 ` Mojca Miklavec
2005-07-22 11:30                   ` Christopher Creutzig
2005-07-22 12:05                     ` Hans Hagen
2005-07-22 22:20                     ` Mojca Miklavec
2005-07-25 15:58                       ` Henning Hraban Ramm
2005-07-25 23:49                       ` Hans Hagen
2005-07-17 20:37     ` Hans Hagen
2005-07-17 21:51       ` Henning Hraban Ramm
2005-07-17 22:36         ` Hans Hagen
2005-07-18 16:18           ` Visual Debugging (was: Basic question) Henning Hraban Ramm
2005-07-18 20:44             ` Brooks Moses
2005-07-18 21:41               ` Visual Debugging 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=42D746BE.3010101@mail.ru \
    --to=radhelorn@mail.ru \
    --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).