9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dimitry Golubovsky <golubovsky@gmail.com>
To: mirtchov@cpsc.ucalgary.ca
Cc: 9fans@cse.psu.edu
Subject: [9fans] plan9 and the Unicode Consortium definitions
Date: Fri, 19 Aug 2005 11:23:15 -0400	[thread overview]
Message-ID: <bcba51a050819082312f666e2@mail.gmail.com> (raw)

Andrey,

Andrey wrote:

>> I am just wondering whether any API to access more complete set of
>> character properties defined by Unicode.org is available in Plan9.

>you mean things like diacritics?

I mean character categories defined in 

http://www.unicode.org/Public/4.1.0/ucd/UCD.html#General_Category_Values

Abbr.  Description
 
Lu Letter, Uppercase 
Ll Letter, Lowercase 
Lt Letter, Titlecase 
Lm Letter, Modifier 
Lo Letter, Other 
Mn Mark, Nonspacing 
Mc Mark, Spacing Combining 
Me Mark, Enclosing 
Nd Number, Decimal Digit 

etc., total about 30 or so. isxxxrune distinguishes only among 5 categories.

This would probably inlcude diacritics, but my question was more
general (maybe even philosophical): there exists a recommended set of
Unicode character properties, APIs, and interfaces (Unicode.org).
Plan9 which probably influenced some aspects of Unicode to be
implemented in other systems does not follow. Is there any historical
/political /technical /other reason? Related man pages mention "The
Unicode Standard" though in SEE ALSO section.

What is more interesting to me (technically, as I asked in my first
message) - is 16-bitness of runes hardcoded anywhere in the kernel, or
only in libc?

-- 
Dimitry Golubovsky

Anywhere on the Web


             reply	other threads:[~2005-08-19 15:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-19 15:23 Dimitry Golubovsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-19 14:51 Dimitry Golubovsky
2005-08-19 15:00 ` Christoph Lohmann
2005-08-19 15:03 ` andrey mirtchovski
2005-08-19 15:29 ` Rob Pike

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=bcba51a050819082312f666e2@mail.gmail.com \
    --to=golubovsky@gmail.com \
    --cc=9fans@cse.psu.edu \
    --cc=mirtchov@cpsc.ucalgary.ca \
    /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).