On Sat, Jan 08, 2011 at 11:44:56AM +, Roger Leigh wrote:
> > Can this please get done (adding a C.UTF-8 locale)? It is absolutely
> > required for writing shell scripts that handle UTF-8 data, if you want
> > those shell scripts to have anything like portable or reliable
> > behavior.
>
hello,
Can this please get done (adding a C.UTF-8 locale)? It is absolutely
required for writing shell scripts that handle UTF-8 data, if you want
those shell scripts to have anything like portable or reliable
behavior.
--
- David A. Holland / dholl...@eecs.harvard.edu
--
To UNSUBSCRIBE,
On Sat, Jan 08, 2011 at 12:25:33AM +, Colin Watson wrote:
> > Where should I file a report that C.UTF-8 should be a supported
> > locale?
>
> glibc, I imagine.
Ok.
> > Or is that so anathema to the UTF-8 ideologues that it's not worth
> > trying to even ask for?
>
> I suspect that u
On Fri, Jan 07, 2011 at 11:24:04PM +, Debian Bug Tracking System wrote:
> > The message you're seeing in the debug output indicates that
> > setlocale(3) returned an error, which is not specific to man.
>
> Given this, I'm going to close the bug. Applications which cope with
> C.UTF-8 ar
Package: e2fsprogs
Version: 1.41.3-1
Severity: important
Under unclear circumstances fsck ignores the -t fstype argument, and
instead runs the fsck for a filesystem type of its own choosing. It
looks from strace as if it's examining the superblock and assuming it
understands what it sees.
First,
Package: e2fsprogs
Version: 1.41.3-1
Severity: normal
fsck does not behave sanely if asked to fsck an object at a
nonabsolute path.
To wit, first set up an ext2 image:
# mkdir /tmp/test
# cd /tmp/test
# dd if=/dev/zero of=image bs=4096 count=1024
# mke2fs image
Now run:
# fsck
Package: console-data
Version: 2:1.07-11
Severity: normal
Tags: l10n
With the default console setup (I have not changed anything since
installing) and the default LANG=en_US.UTF-8 locale setting, running
gcc on the console (on a file with suitable errors) produces square
block glyphs where there
Package: man-db
Version: 2.5.2-4
Severity: minor
Tags: l10n
If LANG is set to en_US.UTF-8, some man pages, such as cal(1), are
rendered with Unicode hyphens. If LANG is set to C.UTF-8, however,
this does not happen and ASCII dashes appear instead.
This is not a problem in groff because if groff
8 matches
Mail list logo
