From: Hans Hagen <pragma@wxs.nl>
Subject: utf 8 / test file
Date: Sat, 07 Dec 2002 12:38:46 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20021207123223.0254e040@server-1> (raw)
Hi,
I posted
http://www.pragma-ade.com/temp/titus.pdf
now, one thing with unicode (utf) is that support needs to have an
associated font / language switch.
Traditionally, tex font mechanisms have been complicated by the fact that
there are many shapes per font and math has to be dealt with.
If we're dealing with say sanskrit, is it then safe to assume that
(1) we can switch to the language (if not yet done) when we encounter a
unicode from the associated char/glyph range
(2) can we assume that a relatively simple font mechanism is used
(normal,bold,slanted)
(3) can we assume that only a few (possibly derived from unicode) fonts are
used, or at least one main type of font per language
(4) can we standardize on utf-8 [and assume some preprocessor if not]
[let's try to deal with the practical, so what's the practical usage]
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next reply other threads:[~2002-12-07 11:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-07 11:38 Hans Hagen [this message]
2002-12-08 20:38 ` Simon Pepping
2002-12-08 23:26 ` Hans Hagen
2002-12-09 9:40 ` Taco Hoekwater
2002-12-09 10:40 ` Re[2]: " Giuseppe Bilotta
2002-12-09 11:30 ` Hans Hagen
2002-12-09 20:32 ` Simon Pepping
2002-12-09 20:44 ` Simon Pepping
2002-12-10 9:54 ` 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=5.1.0.14.1.20021207123223.0254e040@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).