From: Mojca Miklavec <mojca.miklavec1@email.si>
Subject: (Con)TeX(t), Unicode and accented characters
Date: Mon, 20 Dec 2004 21:02:30 +0100 [thread overview]
Message-ID: <41C72FD6.3030807@email.si> (raw)
Here's a short version of my question:
How do I enable unicode encoded characters (just normal accented latin
characters) to be typeset in (any font) in ConTeXt, like the
\usepackage[utf8]{inputenc} in LaTeX?
And here the long one:
************************************************************************
I don't really understand how accented characters are typeset in
(Con)TeX(t). One of the main reasons for switching to LaTeX (maybe 8
years ago) someone mentioned was: "You don't have to worry about
accented characters. You can make any accented character and it will
work all over the world." (We actually did have lots of problems with MS
Word and web browsers at that time.) And it was true.
But when I switched to ConTeXt I came against that problem again.
In LaTeX I used
\v{c}\v{s}\v{z}
at first, later
\usepackage{csz} ... "c"s"z
(which works pretty much the same as "a"o"u in German)
and finally (when someone told me about that possibility)
\usepackage[utf8]{inputenc} ... čšž
As I didn't know how to use any other the font, I always used CMR, the
default, so I didn't have problems with exotic fonts either.
************************************************************************
But here we come to ConTeXt.
For the German "Umlaut", \"{a}\"{o}\"{u} (äöü), this was satisfactory:
\useencoding[windows-1250]
\mainlanguage[de]
For \v{c}\v{s}\v{z} (čšž) this wasn't the case, so a proposed solution
from another ConTeXt user was:
% output=pdf -translate-file=cp1250cs
\setupbodyfont
[csr,ams,rm]
What I don't really understand: why did the Chech TUG have to design
*their own font*, csr, (or made changes to cmr) if accented characters
worked perfectly already in plain TeX?
The second problem: This works under Windows when typesetting in code
page 1250. How can I use accented characters if text is typeset in
Unicode (or latin2) in Linux?
The third problem: How do I typeset '\v{c}' in some other font? I do
understand that it may not function in just any font since someone has
to tell the computer how the accented characters are built, but as long
as \v{c} works, there's no reason for
\useencoding[utf8]
and then continuing with unicode encoded characters not to produce the
desired result.
Thank you,
Mojca
next reply other threads:[~2004-12-20 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 20:02 Mojca Miklavec [this message]
2004-12-20 20:52 ` Hans Hagen
2004-12-20 21:35 ` Mojca Miklavec
2004-12-20 22:16 ` VnPenguin
2004-12-21 7:56 ` r.ermers
2004-12-21 10:01 ` Adam Lindsay
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=41C72FD6.3030807@email.si \
--to=mojca.miklavec1@email.si \
--cc=mojca.miklavec@guest.arnes.si \
--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).