Jim Meyering wrote: > Pádraig Brady <[EMAIL PROTECTED]> wrote: > > >>Jim Meyering wrote: >> >>> -g, --general-numeric-sort compare according to general numerical value >>> -M, --month-sort compare (unknown) < `JAN' < ... < `DEC' >>> -n, --numeric-sort compare according to string numerical value >>> -r, --reverse reverse the result of comparisons >> >>These 4 deal with specific order which I don't think uniq should worry about? > > > You're right about --reverse. Thanks. > > However, the others change sort's idea of which values are equal, > so they are relevant. For -g, 0.0 == 0 == 00, etc. > For -M, FEB == feb == Feb, etc. > For -n, 00 == 0. > > The idea is to be able to use uniq with the same keyspec options > as you used when sorting the data. > That means the command-line options listed above as well as the > key spec modifier options like b, d, g, M etc. used e.g., in -k 1b,1 -k 2n.
Right, thanks. >>uniq can be efficient and assume LANG=C always as >>it need only care if adjacent items match or not. >>Assuming LANG=C may be an issue for --ignore-case though? >>However I notice v5.2.1 at least only seems to handle ascii: >> >>$ LANG=ga_IE.utf8 uniq -i < Pádraig >>Pádraig >>PÁdraig > > > Yes, that's still a problem. > Would you like to work on it? Hmm looks like that's done already? http://www.openi18n.org/subgroups/utildev/dli18npatch2.html $ cat Pádraig Pádraig PÁdraig $ ./i18n-uniq -i < Pádraig Pádraig _______________________________________________ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
