From: "Joel Salomon" <joelcsalomon@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] combining characters
Date: Sun, 21 May 2006 13:52:11 -0400 [thread overview]
Message-ID: <7871fcf50605211052ye80eea5w29410be3d43f1911@mail.gmail.com> (raw)
In-Reply-To: <5c6e0490f9e7da28ba8273f8f2eb072b@quanstro.net>
On 5/19/06, quanstro@quanstro.net <quanstro@quanstro.net> wrote:
> On Fri May 19 17:55:50 CDT 2006, joelcsalomon@gmail.com wrote:
> > Take Hebrew, for instance: 27 letters (including the 5 final forms) +
> > a few alternate forms, 15 vowel marks, 25+ cantillation marks --
> > that's more than 10,000 combinations right there.
>
> i don't know hebrew very well, but are you confusing glyphs with characters?
>
> for example arabic has three letter forms: initial, final and medial.
> (there is a different shape for the the same letter at the beginning, middle
> and end of the word.)
>
> so in arabic, a good renderer would need three glyphs for each codepoint.
Hebrew final forms are not much of a problem; they are separate
characters, typed with different keys. It's the vowel marks needed
sometimes (whn yu cnnt nfr th vwls frm cntxt) and the cantillation
marks needed for Biblical text that make for the code space explosion.
Arabic text rendering—for readable plain text, not just for "fancy"
typesetting—requires yet another clever set of algorithms.
I don't know that there's a way to manage this complexity without
giving "fonts" their own context-aware programming language, like
TrueType.
--Joel
--
It reverses the normal flow of conversation.
> What's wrong with top-posting?
> > Top-posting.
> > > What's the biggest scourge on plain text email discussions?
next prev parent reply other threads:[~2006-05-21 17:52 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 14:36 rog
2006-05-19 15:11 ` quanstro
2006-05-19 16:16 ` quanstro
2006-05-19 21:03 ` Jack Johnson
2006-05-19 21:26 ` Lluís Batlle i Rossell
2006-05-19 21:21 ` quanstro
2006-05-19 21:45 ` jmk
2006-05-19 21:57 ` Francisco J Ballesteros
2006-05-19 21:51 ` quanstro
2006-05-19 22:04 ` Francisco J Ballesteros
2006-05-19 22:16 ` quanstro
2006-05-19 22:34 ` Roman Shaposhnick
2006-05-19 22:35 ` quanstro
2006-05-19 23:40 ` Roman Shaposhnick
2006-05-19 23:43 ` quanstro
2006-05-20 0:12 ` Roman Shaposhnick
2006-05-20 0:13 ` quanstro
2006-05-20 0:43 ` Roman Shaposhnick
2006-05-20 0:44 ` quanstro
2006-05-20 4:13 ` Jack Johnson
2006-05-21 18:10 ` Joel Salomon
2006-05-21 18:12 ` Joel Salomon
2006-05-25 0:23 ` Roman Shaposhnick
2006-05-27 19:41 ` Dan Cross
2006-05-27 20:15 ` Victor Nazarov
2006-05-28 1:49 ` LiteStar numnums
2006-05-20 0:59 ` andrey mirtchovski
2006-05-20 0:51 ` quanstro
2006-05-20 1:43 ` Roman Shaposhnick
2006-05-20 1:38 ` Roman Shaposhnick
2006-05-20 1:59 ` Federico Benavento
2006-05-25 0:24 ` Roman Shaposhnick
2006-05-20 3:59 ` geoff
2006-05-20 10:56 ` Lucio De Re
2006-05-20 11:04 ` Lluís Batlle i Rossell
2006-05-20 0:18 ` andrey mirtchovski
2006-05-21 18:11 ` Joel Salomon
2006-05-19 22:40 ` andrey mirtchovski
2006-05-19 22:36 ` quanstro
2006-05-19 23:28 ` andrey mirtchovski
2006-05-19 22:54 ` Joel Salomon
2006-05-19 22:50 ` quanstro
2006-05-20 1:05 ` Skip Tavakkolian
2006-05-21 17:52 ` Joel Salomon [this message]
2006-05-22 4:04 ` Jack Johnson
2006-05-19 22:29 ` Lluís Batlle i Rossell
2006-05-19 22:22 ` quanstro
2006-05-19 22:45 ` Lluís Batlle i Rossell
2006-05-22 22:55 erik quanstrom
2006-05-23 4:58 ` Jack Johnson
2006-05-23 10:07 erik quanstrom
2006-05-23 14:24 ` LiteStar numnums
2006-05-23 17:07 ` plan9
2006-05-23 17:11 ` Ronald G Minnich
2006-05-23 18:53 ` Charles Forsyth
2006-05-23 20:09 ` Harri Haataja
2006-05-25 0:31 ` Roman Shaposhnick
2006-05-25 2:34 ` Andy Newman
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=7871fcf50605211052ye80eea5w29410be3d43f1911@mail.gmail.com \
--to=joelcsalomon@gmail.com \
--cc=9fans@cse.psu.edu \
/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).