From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] [RFC] fonts and unicode/utf [TeX]
Date: Sat, 25 Jun 2011 11:11:50 -0400 [thread overview]
Message-ID: <b28d999f4d005fbed20e0e756a1dd12c@ladd.quanstro.net> (raw)
In-Reply-To: <20110625150327.GA425@polynum.com>
On Sat Jun 25 11:01:38 EDT 2011, tlaronde@polynum.com wrote:
> On Sat, Jun 25, 2011 at 08:19:40AM -0400, erik quanstrom wrote:
> > > So for now, TeX is kept 8 bits. I make no assumption for the encoding
> > > (and user has to feed "8 bits encoding" to TeX; ASCII users have nothing
> > > to change; others, if they want to use directly another 8 bits encoding
> > > (ex.: directly accented letters latin1 code) have to tcs(1) the file
> > > first.
> >
> > i am not clear on what "the file" means in this context. do you mean
> > the .tex input file or font files?
>
> I mean the .tex file. The font files as seen by TeX are only the metrics
> tfm, and they are binaries.
so are you planning on hiding this conversion within the tex
executable or some shell script fronting the executable?
that would work. but letting ancient and deprecated
latin1 escape into editors, &c. would be a mistake.
- erik
next prev parent reply other threads:[~2011-06-25 15:11 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 [this message]
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=b28d999f4d005fbed20e0e756a1dd12c@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).