9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Karljurgen Feuerherm" <kfeuerherm@wlu.ca>
To: <9fans@9fans.net>
Subject: [9fans] Lex, Yacc, Unicode Plane 1
Date: Thu, 28 Jan 2010 14:43:12 -0500	[thread overview]
Message-ID: <4B61A280020000CC0001D4A1@wlgw07.wlu.ca> (raw)

[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]

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ürgen 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)

[-- Attachment #2: HTML --]
[-- Type: text/html, Size: 1430 bytes --]

             reply	other threads:[~2010-01-28 19:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28 19:43 Karljurgen Feuerherm [this message]
2010-01-28 20:05 ` erik quanstrom
2010-01-28 20:46 ` geoff
2010-01-28 20:59   ` Karljurgen Feuerherm
2010-01-28 21:20     ` geoff
2010-01-28 21:51       ` Karljurgen Feuerherm
2010-01-28 22:07         ` ron minnich
2010-01-28 22:19           ` hiro
2010-01-28 22:34             ` Karljurgen Feuerherm
2010-01-28 22:56           ` erik quanstrom
2010-01-28 23:38             ` Federico G. Benavento
2010-01-28 23:42       ` erik quanstrom
2010-01-29  0:08         ` Karljurgen Feuerherm
2010-01-29  0:19       ` Rob Pike
2010-01-29  0:24         ` erik quanstrom
2010-01-29  0:36           ` Russ Cox
2010-01-29  0:42             ` erik quanstrom
2010-01-29  0:58               ` Russ Cox
2010-01-29  6:08             ` erik quanstrom
2010-01-29  6:18               ` Justin Jackson
2010-01-29 14:36                 ` Ethan Grammatikidis

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=4B61A280020000CC0001D4A1@wlgw07.wlu.ca \
    --to=kfeuerherm@wlu.ca \
    --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).