From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Font/UTF-8 input question
Date: Wed, 28 Apr 2004 19:31:00 +0200 [thread overview]
Message-ID: <6.0.1.1.2.20040428192805.01cf0e60@server-1> (raw)
In-Reply-To: <408E518C.3000806@physik.fu-berlin.de>
At 14:26 27/04/2004, you wrote:
>Hello,
>
>I'd like to use a Unicode font such as Linux Libertine [1]. Besides things
>which should happen "automatically" like ligatures, I want to enter all
>characters directly in the UTF-8 file (including those wierd characters).
>I remember that there is some UTF-8 support in ConTeXt, but I don't
>remember the details. Is it possible to simply enter a character such as
>U+FB02 or do I have first to adapt both the input encoding and the font
>encoding files?
in prinicple regime utf should work for the input; characters are mapped
onto their symbolic names so fonts should go ok
with regards to unicode fonts: you need to create a 255 char variant (i.e.
ttftoafm and alike); i'm sure that some of the open type font guru;s on
this list can tell you how to proceed there
Hans
prev parent reply other threads:[~2004-04-28 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 12:26 Tobias Burnus
2004-04-28 17:31 ` Hans Hagen [this message]
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=6.0.1.1.2.20040428192805.01cf0e60@server-1 \
--to=pragma@wxs.nl \
--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).