From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] [RFC] fonts and unicode/utf [TeX]
Date: Mon, 27 Jun 2011 08:36:35 -0400 [thread overview]
Message-ID: <9308c52f360f6274e0730399741278ce@ladd.quanstro.net> (raw)
In-Reply-To: <20110627114856.GA7099@polynum.com>
> But I don't want to have the obligation to "know" 65536 signs to
> express what I want to express. I'm sorry, but I think that the
> main majority (remember that for latin1/latin2 accented letters
> are just variants so need less "user memory" than plain different
> characters) can do with (less than) 256 signs blocks, and switch
> fonts when "speaking" about special things (the switch can be
> automatic by the way). As far as TeX is concerned, all the control
> codepoints (positions) are useless in the fonts. There is still
> availbale room even if for the latin1 encoded tfm built for (next)
> kerTeX from PostScript core.
there are currently 0x10ffff+1 codepoints (1114112), not 65536,
but only 23669 + the large chinese blocks are currently defined.
but anyway, i think you are missing the point. every one of those
codepoints is used, or was used in human written communication.
the fact that you or i probablly don't know them all is beside the
point entirely.
there are 600000 words in the oxford english dictionary. i don't
know them all. let's suppose i had the power to eliminate all
the ones that i don't know. wouldn't that be a horrible idea?
then i would not be able to learn any new words. odious.
so with unicode. if you strip out all the languages you don't know
by restricting yourself to the latin1 codepoints [0, 256), then you
can't easily add, say, greek or sumerian codepoints should you or
anyone else need them.
since, as you can see, there is a 1:1 identity mapping between latin1
and unicode codepoints [0, 256), i don't see why one wouldn't
give oneself the option to increase this subset to cover more ground.
i use alphas, arrows, math symbols, etc. quite often in code. and
even more often when i used to use tex. it's really quite a drag to
read \alpha instead of “α.”
> Does a whole Unicode "Times-Roman" font makes sense? Ideograms in
> "Times-Roman"?
i get confused on terms. i think the right term is typeface.
extended fonts collections of a given typeface covering very
wide sections of unicode do exist and are sold by the major
font vendors.
i don't think that it's too hard to imagine that one can make
most symbols look compatable enough. in fact, i'm using a font
with ~32000 glyphs on my plan 9 terminal right now.
and there's no penalty for having that many glyphs. it just
means that my font file as a couple hundred subfonts. these
are only open if needed. typically only 3 subfonts are open
at any one time.
- erik
next prev parent reply other threads:[~2011-06-27 12:36 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 12:17 tlaronde
2011-06-16 16:49 ` Russ Cox
2011-06-16 17:37 ` tlaronde
2011-06-16 18:43 ` Bakul Shah
2011-06-16 19:20 ` tlaronde
2011-06-16 17:43 ` tlaronde
2011-06-17 14:18 ` Joel C. Salomon
2011-06-17 15:37 ` tlaronde
2011-06-17 18:07 ` Joel C. Salomon
2011-06-17 18:37 ` tlaronde
2011-06-19 14:21 ` erik quanstrom
2011-06-19 14:07 ` erik quanstrom
2011-06-19 16:34 ` tlaronde
2011-06-19 18:01 ` tlaronde
2011-06-19 22:38 ` erik quanstrom
2011-06-20 11:18 ` tlaronde
2011-06-20 21:53 ` erik quanstrom
2011-06-21 10:56 ` tlaronde
2011-06-24 23:05 ` Mauricio CA
2011-06-25 6:50 ` tlaronde
2011-06-25 12:19 ` erik quanstrom
2011-06-25 15:03 ` tlaronde
2011-06-25 15:11 ` erik quanstrom
2011-06-25 16:33 ` tlaronde
2011-06-25 16:34 ` Mauricio CA
2011-06-25 17:11 ` tlaronde
2011-06-25 18:43 ` Michael Kerpan
2011-06-26 7:57 ` tlaronde
2011-06-27 1:01 ` Michael Kerpan
2011-06-27 11:48 ` tlaronde
2011-06-27 12:36 ` erik quanstrom [this message]
2011-06-27 14:38 ` Karljurgen Feuerherm
2011-06-27 17:20 ` tlaronde
2011-06-27 17:34 ` erik quanstrom
2011-06-27 18:01 ` tlaronde
2011-06-27 21:17 ` Michael Kerpan
2011-06-28 11:25 ` tlaronde
2011-06-27 23:45 ` Karljurgen Feuerherm
2011-06-27 23:48 ` erik quanstrom
2011-06-28 11:19 ` tlaronde
2011-06-28 11:32 ` tlaronde
2011-06-28 12:16 ` erik quanstrom
2011-06-29 23:43 ` Karljurgen Feuerherm
2011-06-30 13:02 ` tlaronde
2011-06-30 13:14 ` erik quanstrom
2011-06-30 13:47 ` tlaronde
2011-06-30 14:51 ` Karljurgen Feuerherm
2011-06-30 15:22 ` Michael Kerpan
2011-06-30 16:25 ` tlaronde
2011-06-30 16:31 ` erik quanstrom
2011-06-30 17:00 ` tlaronde
2011-06-30 17:12 ` tlaronde
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=9308c52f360f6274e0730399741278ce@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).