[ksh93-integration-discuss] Re: [ast-users] Two problems with Unicode characters in ksh93

[Roland Mainz]

Glenn Fowler wrote:
> On Fri, 25 Aug 2006 16:03:38 +0200 I. Szczesniak wrote:
[snip]
> note that \u takes up to 8 hex digits, so the 2nd "\u9836" using decimal
> will treat 9836 as hex, and ...

I just did take a look at the code - it seems to support something like
"\u[<value>]", too - wouldn't that be better to document this as the
preferred way to specifc unicode values ? IMO this may be less
error-prone compared to something like $ (s="escape" ; printf "\u360$s")
# (which would AFAIK be interpreted as "\u360e" instead of the
(intended) "\u360" ...

> > How do I specify Unicode outside the Basic Multilingual Plane (BMP,
> > which uses values larger than 2^16) in ksh93?
> 
> will handle up to 2^32 bits

What about the idea with "\w" to have a way to specify a widechar value
(CC:'ing Ienup and i18n-discuss at opensolaris.org for feedback. The idea
was to add "\wXXXX" to allow someone to specify a locale-specific
widechar value in a similar way how "\uXXXX" can be used to specific a
unicode value in ksh93's "printf" command (see
https://mailman.research.att.com/pipermail/ast-users/2006q3/001220.html)
- which may be usefull for locales like *.GB18030, ja_JP.PCK etc.) ?

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz at nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 7950090
 (;O/ \/ \O;)