We came across something that appears to be a bug as opposed to an unintended design feature.
If you consider the following source file (named sort.txt in my example): M=L MIK M- M-K M= MIK M-A miw...@avalanche:/home/miwarn> sort sort.txt M= M- M-A MIK MIK M-K M=L miw...@avalanche:/home/miwarn> I am expecting the output to come out in ASCII sorted order. If the first 2 rows were correctly ordered, the last row (M=L) should actually be the second row which would be followed by all of the (M-, M-A, M-K rows). The reason it appears to be a bug is because it is ignoring these printable ASCII characters when I don't think it should be. The whole part about some entries with a dash or an equal sign coming before the entries with an I in the second character and some coming after is also quite strange. Is this a bug that has been reported and corrected already? Michael D. Warner | Solution/Software Developer SD Acxiom Financial Services 00-1-309-689-1470 home Peoria, IL | U.S.A. | www.acxiom.com *************************************************************************** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. ****************************************************************************
<<image001.gif>>