From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@9fans.net From: Mauricio CA Date: Sat, 25 Jun 2011 16:34:17 +0000 Message-ID: References: <20110616121700.GA9131@polynum.com> <9556bc097d90b774c37c16af5a7c20eb@brasstown.quanstro.net> <20110619163458.GA424@polynum.com> <3c7e401c771bdd0d9bd8950ceb60eb9e@ladd.quanstro.net> <20110620111845.GA540@polynum.com> <76aac2169637c7af09dcd0b368aa0c7a@ladd.quanstro.net> <20110621105626.GA536@polynum.com> <20110625065017.GA638@polynum.com> <522e1e2a38aa18c291305563d362abfe@ladd.quanstro.net> <20110625150327.GA425@polynum.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit User-Agent: slrn/0.9.9p1 (Linux) Subject: Re: [9fans] [RFC] fonts and unicode/utf [TeX] Topicbox-Message-UUID: f5cad1b6-ead6-11e9-9d60-3106f5b1d025 > Since TeX is "8 bits", the tex file must have characters encoded in > 8 bits, with the not control positions of the first half being, after > perhaps mapping defined at compile time (can be remapped at user level > but with apparently "strange" macro commands), conforming to ASCII--- > used as litterals but also for the primitives. Is it possible to change the representation of a character from an 8 bits char to, say, a 32 bits integer? If those integers are still mapped to the existing 8 bits font metrics, wouldn't the basic engine be kept the same? This probably means extending the syntax of a few control sequences denoting characters, though. Best, MaurĂ­cio