From: Thomas A.Schmitz <thomas.schmitz@uni-bonn.de>
Subject: Re: chancery font
Date: Sun, 3 Apr 2005 22:22:37 +0200 [thread overview]
Message-ID: <1e598136798675448f1f89689e76d69d@uni-bonn.de> (raw)
In-Reply-To: <42AE6611@webmail.colostate.edu>
On Apr 3, 2005, at 9:40 PM, Idris Samawi Hamid wrote:
> Hi guys,
>
> Ok, I certainly did _not_ intend to start a flame war, was just
> dreaming out
> loud:-))
Idris,
no flame war intended! I know that we have very similar interests (btw:
how's "critical editions in ConTeXt" doing?), that's why I stated what
I feel about it. (For the manual: have you looked in your inbox
lately?)
During the last weeks, I have written a perl script to create an
automatic encoding vector for ttf (Unicode) fonts with Greek letters. I
have spent way too much time on it. It works reasonably well, but I
always have to look at things and correct stuff manually. Font
designers are too [insert favorite swearword here] to give decent names
to their glyphs, and since we need those names for the encoding, it's
hard to make things happen automatically. Fonts claim to follow the
Unicode standard, but then have glyphs in the wrong place. Some
designers even modify the standard Adobe names, so you can't even use
the normal ec or texnansi-encoding.
>
>
> I have even more difficult issues with Arabic;-)
Yeah, I can believe that.
>>
>
> Hmm, seems we've heard the same comment about Linux in the pre-KDE
> days:-)
Tell you what: I think right now the same is true for linux. As long as
you're satisfied with the standards some distribution gives you, you
might get past the CLI. But try to integrate a piece of unusual
hardware, or modify settings, and presto, you need the terminal and a
basic understanding of Unix.
> Seriously, there is room in the TeX world for a creative gui approach,
> and
> ConTeXt would be a much better candidate than LaTeX for that to work.
> Yes,
> this is just a dream for now...
Well, let's dream and not take this further. Bedtime over here in
Europe...
All best
Thomas
next prev parent reply other threads:[~2005-04-03 20:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-03 19:40 Idris Samawi Hamid
2005-04-03 19:54 ` Paul Tremblay
2005-04-03 20:22 ` Thomas A.Schmitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-16 14:13 Enrique Laya
2005-04-03 20:39 Idris Samawi Hamid
2005-04-03 18:46 Idris Samawi Hamid
2005-04-03 18:45 Idris Samawi Hamid
2005-04-03 20:25 ` Ciro Soto
2005-04-03 21:06 ` h h extern
2005-04-03 16:15 Idris Samawi Hamid
2005-04-03 16:42 ` Rob Ermers
2005-04-03 16:57 ` Paul Tremblay
2005-04-03 17:10 ` Thomas A.Schmitz
2005-04-02 22:33 Idris Samawi Hamid
2005-04-02 21:21 Idris Samawi Hamid
2005-04-01 8:37 btex-etex Jiri Polcar
2005-04-02 16:52 ` chancery font Ciro Soto
2005-04-02 17:27 ` Idris Samawi Hamid
2005-04-02 17:52 ` Willi Egger
2005-04-02 18:29 ` Ciro Soto
2005-04-02 19:21 ` Idris Samawi Hamid
2005-04-02 20:00 ` Ciro Soto
2005-04-02 21:22 ` Adam Lindsay
2005-04-02 23:33 ` Ciro Soto
2005-04-03 14:03 ` Rob Ermers
2005-04-03 14:57 ` Adam Lindsay
2005-04-03 16:22 ` Ciro Soto
2005-04-03 19:41 ` h h extern
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=1e598136798675448f1f89689e76d69d@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).