Tim Bray wrote: > On Nov 2, 2007, at 9:43 AM, Bart Smaalders wrote: > > Spaces are of course the most commom example. But other characters > > may > > be desirable as well. > > > > Do we encode characters in a form representable in ascii locales, > > or do > > we use raw byte codes? Since UTF-8 allows control characters, line > > oriented parsing is difficult for arbitrary filenames unless escaping > > is done. It's not just spaces that are the problem, it's any other > > control characters... we'll need to escape characters so that they > > can be rationally displayed in multiple locales... > > I'm sorry, you lost me there with "raw byte codes". UTF-8 can > represent any of UTF-8's just over one million code points, using > ASCII bytes to represent ASCII characters and no ASCII bytes in > representing non-ASCII characters. Are you suggesting that someone > might include a \n in a filename? Gack... basically *everything* > would break.
Erm... no. If you set IFS='' (or quote variable expansions) then any POSIX shell should be able to handle this (see my earlier note abotu $''-style string literals, e.g. $'foo\n\tblabla\vxyz' works fine here). ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
