From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] [RFC] fonts and unicode/utf [TeX]
Date: Thu, 16 Jun 2011 21:20:12 +0200 [thread overview]
Message-ID: <20110616192012.GA12130@polynum.com> (raw)
In-Reply-To: <20110616184328.0A64BB827@mail.bitblocks.com>
On Thu, Jun 16, 2011 at 11:43:28AM -0700, Bakul Shah wrote:
> > Modifying TeX to accept utf as input (I mean the compiler/interpreter by
> > itself; not macros), converting to rune and then using 16 bits à la math
> > mode to switch inside a font family to the "correct" 256 vector is
> > something that, for a first step, seems to me both reasonable and
> > simple.
>
> What about XeTeX? It is a merge of TeX with Unicode and
> modern font tech. Works with OpenType Fonts.
I will give it a look. The decision will depend on:
1) The licence: if it is GPL, I will not touch it even with a long
spoon...
2) If the core modifications are separated enough from the kpathsea
and so on dance.
3) The nature of the solution.
There is another program I have to give it a look: John Hobby has given
me the information about an evolution of his MetaPost. It is original
AT&T and LGPL, so for the licence it's OK. For the modifications, I will
have to look.
So just to say that I'm not discarding existing solutions by principle.
If XeTeX does answer correctly---to my taste---to the problem, why not?
But since there is now almost only the lost needle in kerTeX, I will not
add back hay.
And just for the record once more: LaTeX can work with kerTeX; so even
the unicode.sty hack Russ Cox wrote about can work with kerTeX. User has
all the rope he can dream of...
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
next prev parent reply other threads:[~2011-06-16 19:20 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 [this message]
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
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=20110616192012.GA12130@polynum.com \
--to=tlaronde@polynum.com \
--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).