cc: [email protected] Subject: Re: Re: [ast-users] Re: read -d command not supporting non-ASCII/Unicode chars --------
> 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 > The problem is that ksh93 uses the sfio library function sfgetr() to read a record and this has to be modified to handle multi-byte. Secondly, when reading from a terminal, you can't just set the VEOL character to be the delimiter since it is now multi-byte so it may required a raw mode read. We plan to made this changes after the next update which we hope to release at the end of this week. David Korn [email protected] _______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
