[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Is lack of UTF support an RC bug? [was: Bug#386299: ekg2: Plugin/program compilation option mismatch]

On Thu, Sep 07, 2006 at 06:25:26PM +0100, Marcin Owsiany wrote:
> > > Try running it in some iso-8859 locale.

> > That's not an acceptable answer, given that almost all locales for etch will
> > be Unicode by default.  This makes the package unreleasable.  Of course, the
> > package seems to only be in experimental at all, so I don't see why you
> > would bother to downgrade the bug...

> It doesn't matter for ekg2, which will stay in experimental for quite a
> while I'm afraid, but it is important for at least two other of my
> packages (which are in etch) which don't support UTF-8 at all. And I'm
> reasonably sure they are not the only packages in etch which don't
> support UTF.

> Who decided that we should just drop them all? After all generating a
> non-UTF locale and setting an environment variable isn't a very
> difficult workaround? I mean, when has lack of UTF support become an
> RC-bug? Charset support is not even mentioned in the policy, other than
> for debian/changelog.

> Don't get me wrong, I'm not against UTF-8, but just dropping everything
> that doesn't support it, without a former warning, sounds ridiculous.

It's already been pointed out that there's a big difference between "won't
display non-ASCII characters correctly in a UTF-8 locale" and "won't work at
all in a UTF-8 locale".  There's no excuse for the latter; and as Unicode
locales *are* the default for almost all new installs of etch, this does
make such a package mostly unusable.

Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature

Reply to: