From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <4B61A280020000CC0001D4A1@wlgw07.wlu.ca> Date: Thu, 28 Jan 2010 14:43:12 -0500 From: "Karljurgen Feuerherm" To: <9fans@9fans.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=__Part6A404DC0.0__=" Subject: [9fans] Lex, Yacc, Unicode Plane 1 Topicbox-Message-UUID: c9b6534e-ead5-11e9-9d60-3106f5b1d025 This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --=__Part6A404DC0.0__= Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hello, =20 A colleague put me on to Plan9, some of whose online documentation I have read with interest, in particular the =22Hello World=22 discussion as it relates to Unicode/UTF-8. =20 I=27m one of the authors of the Cuneiform proposal now encoded under Unicode (see block U+12000), and I=27m interesting in lex/yacc-like parsing of Unicode input to produce (among other things) Cuneiform output. =20 I realize some of the documentation was written long ago... so I=27m unclear as to whether or not (or how easily) Plan9 (and specifically its lex/yacc software, etc.) handles such things? (this sparked by the references to four hex digits etc.) =20 Many thanks if you can point me in the right direction :) (or to an alternative solution, if need be=21) =20 Best =20 K =20 Karlj=FCrgen G. Feuerherm, PhD Department of Archaeology and Classical Studies Wilfrid Laurier University 75 University Avenue West Waterloo, Ontario N2L 3C5 Tel. (519) 884-1970 x3193 Fax (519) 883-0991 (ATTN Arch. & Classics) --=__Part6A404DC0.0__= Content-Type: text/html; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Content-Description: HTML
Hello,
 
A colleague put me on to Plan9, some of whose online documentation I = have read with interest, in particular the "Hello World" discussion as it = relates to Unicode/UTF-8.
 
I'm one of the authors of the Cuneiform proposal now encoded under = Unicode (see block U+12000), and I'm interesting in lex/yacc-like parsing = of Unicode input to produce (among other things) Cuneiform output.
 
I realize some of the documentation was written long ago... so I'm = unclear as to whether or not (or how easily) Plan9 (and specifically its = lex/yacc software, etc.) handles such things? (this sparked by the = references to four hex digits etc.)
 
Many thanks if you can point me in the right direction :) (or to an = alternative solution, if need be!)
 
Best
 
K
 
Karlj=FCrgen G. Feuerherm, PhD
Department of Archaeology and = Classical Studies
Wilfrid Laurier University
75 University Avenue = West
Waterloo, Ontario N2L 3C5
Tel. (519) 884-1970 x3193
Fax = (519) 883-0991 (ATTN Arch. & Classics)
--=__Part6A404DC0.0__=--