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, 30 Jun 2011 19:12:10 +0200 [thread overview]
Message-ID: <20110630171210.GA1684@polynum.com> (raw)
In-Reply-To: <20110630170048.GA999@polynum.com>
On Thu, Jun 30, 2011 at 07:00:48PM +0200, tlaronde wrote:
>
> This does not preclude the user from directly entering the unicode
> codepoint: in the TFM, if you want, the glyph information is duplicated,
> in the conventional plain TeX position, and as a literal in the unicode
> position.
More precisely (I hope), since the "latin minuscule ae" is duplicated
too in the conventional TeX positions (overwriting only ASCII range
control positions that are useless), the plain TeX conventions work,
while user can also enter directly the unicode for this.
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
prev parent reply other threads:[~2011-06-30 17:12 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
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 [this message]
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=20110630171210.GA1684@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).