On Sat, Apr 10, 2010 at 07:43:39AM -0700, Russ Allbery wrote:
> Osamu Aoki writes:
>
> > Since this test should work in all environment, I think whoever created
> > this test must have chosen LANG=C with reason. I am not even sure if
> > en_US.UTF-8 exists in the test environment.
>
> Lintian g
On Sat, Apr 10, 2010 at 08:15:57AM -0700, Russ Allbery wrote:
> Osamu Aoki writes:
> > On Sat, Apr 10, 2010 at 07:43:39AM -0700, Russ Allbery wrote:
>
> >> My understanding of how man is supposed to work with character
> >> encodings says that we should not need to be doing things like this.
> >>
Osamu Aoki writes:
> My mind is melting ... You are right. Then LANG=en_US.UTF-8 seems to
> be right solution.
Yeah, that's my suspicion too, and I think the LANG=C part predates the
inclusion of a locale in Lintian. Hopefully it won't cause other issues.
--
Russ Allbery (r...@debian.org)
Osamu Aoki writes:
> On Sat, Apr 10, 2010 at 07:43:39AM -0700, Russ Allbery wrote:
>> My understanding of how man is supposed to work with character
>> encodings says that we should not need to be doing things like this.
>> I've been hoping Colin would weigh in on this bug, though, since he
>> kn
Osamu Aoki writes:
> Since this test should work in all environment, I think whoever created
> this test must have chosen LANG=C with reason. I am not even sure if
> en_US.UTF-8 exists in the test environment.
Lintian guarantees that en_US.UTF-8 exists.
> Then I also realized there are manpage
Package: lintian
Version: 2.3.4
Severity: normal
Tags: patch
Since this test should work in all environment, I think whoever created
this test must have chosen LANG=C with reason. I am not even sure if
en_US.UTF-8 exists in the test environment.
Then I also realized there are manpages in many ol
6 matches
Mail list logo
