Jilles Tjoelker wrote:
> On Tue, Jun 07, 2011 at 04:24:43AM +0400, Andrey Chernov wrote:
...
> > Back to the ports: it is not hard to run _any_ port's make
> > or configure with LANG=C directly by the ports Mk system to
> > eliminate that problem.
>
> True, but some ports install scripts with pro
On Tue, Jun 07, 2011 at 11:17:12PM +0200, Jilles Tjoelker wrote:
> In FreeBSD, upper case sorts before lower case, so cases can be
> distinguished this way but all letters may require two ranges. In most
> other operating systems the cases go together so a single range is
> sufficient, but cases ca
On Wed, 8 Jun 2011, Jilles Tjoelker wrote:
maybe another option would be modifying tr to recognize other [new]
environment variables... TR_LANG, TR_LC_ALL, TR_LC_CTYPE and
TR_LC_COLLATE. done that way, things could be set in /etc/make.conf (or
sys.mk), not need any patching, and not interfere
On Wed, Jun 08, 2011 at 09:56:39AM +1200, Atom Smasher wrote:
> the man page makes it clear...
> Translate the contents of file1 to upper-case.
> tr "[:lower:]" "[:upper:]" < file1
> (This should be preferred over the traditional UNIX idiom of ``tr a-z
> A-Z'', sinc
the man page makes it clear...
Translate the contents of file1 to upper-case.
tr "[:lower:]" "[:upper:]" < file1
(This should be preferred over the traditional UNIX idiom of ``tr a-z
A-Z'', since it works correctly in all locales.)
for any other uses, either build
On Tue, Jun 07, 2011 at 04:24:43AM +0400, Andrey Chernov wrote:
> On Tue, Jun 07, 2011 at 12:41:05AM +0200, Jilles Tjoelker wrote:
> > There is a related issue with ranges in regular expressions, glob and
> > fnmatch (likewise unspecified by POSIX outside the POSIX locale), but
> > this is less li
On Tue, Jun 07, 2011 at 12:41:05AM +0200, Jilles Tjoelker wrote:
>
> There is a related issue with ranges in regular expressions, glob and
> fnmatch (likewise unspecified by POSIX outside the POSIX locale), but
> this is less likely to cause problems.
>
You care about ports, but suggested change
A few years ago, when locale support was added to the tr utility,
character ranges (except ones containing one or two octal escapes) were
changed to use the collation order instead of the character code order.
At the time, this matched other implementations of tr and was apparently
somewhat general
8 matches
Mail list logo
