On 23 April 2012 23:29, David Korn <[email protected]> wrote: > Subject: Re: [ast-users] Re: read -d command not supporting non-ASCII/Unicode > chars > -------- > >> Hello, we're encountering a serious bug when migrating some of our >> data processing scripts from bash to ksh93. After a lengthily >> investigation we traced the problem down to ksh93's read command not >> supporting non-ASCII characters as delimiters (read -d) in the Unicode >> locale (en_GB.UTF-8). >> > > Currently, the delimiter must be a one byte character. We plan to > update this in a release later this year.
What exactly is the difficult part? ksh93 already supports one byte delimiters. Non-ASCII characters can both be represented by a wchar_t or a multibyte sequence. The multibyte sequence could be used as C string and this C string could be used as delimiter, i.e. you search for a C string as delimiter instead of a single byte. Lionel _______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
