Hi Colin!
On Mon, 09 Jun 2003, Colin Walters wrote:
> On Mon, 2003-06-09 at 12:05, Henrique de Moraes Holschuh wrote:
> > On Sun, 08 Jun 2003, Wouter Verhelst wrote:
> > > [EMAIL PROTECTED]:~$ echo $LANG
> > > nl_BE.UTF-8
> >
> > Is it in locale.gen? Otherwise, you will NOT have the locale infor
On Mon, 2003-06-09 at 12:05, Henrique de Moraes Holschuh wrote:
> On Sun, 08 Jun 2003, Wouter Verhelst wrote:
> > [EMAIL PROTECTED]:~$ echo $LANG
> > nl_BE.UTF-8
>
> Is it in locale.gen? Otherwise, you will NOT have the locale information...
Ah, good call. We should have that in the default loca
On Sun, 08 Jun 2003, Wouter Verhelst wrote:
> [EMAIL PROTECTED]:~$ echo $LANG
> nl_BE.UTF-8
Is it in locale.gen? Otherwise, you will NOT have the locale information...
> which means that uxterm manually ensures that $LANG is set to
> something.UTF-8, since I set my $LANG to nl_BE.
Ick.
--
"O
On Sat, Jun 07, 2003 at 05:58:28PM -0400, Colin Walters wrote:
> [ no need to CC me ]
>
> On Sat, 2003-06-07 at 17:39, Wouter Verhelst wrote:
>
> > No, I'm using bash...
>
> Weird. It works here. What's your $LANG? If you're inputting Unicode
> it should probably be something.UTF-8.
it is:
[ no need to CC me ]
On Sat, 2003-06-07 at 17:39, Wouter Verhelst wrote:
> No, I'm using bash...
Weird. It works here. What's your $LANG? If you're inputting Unicode
it should probably be something.UTF-8.
On Sat, Jun 07, 2003 at 04:17:15PM -0400, Colin Walters wrote:
> On Sat, 2003-06-07 at 15:36, Wouter Verhelst wrote:
>
> > Yeah, but it's not always as good as the legacy support is. For
> > instance, last I tried uxterm (like, 2 minutes ago), I put in a euro
> > sign somewhere. Which appeared cor
On Sat, 2003-06-07 at 15:36, Wouter Verhelst wrote:
> Yeah, but it's not always as good as the legacy support is. For
> instance, last I tried uxterm (like, 2 minutes ago), I put in a euro
> sign somewhere. Which appeared correctly (hurray), but doing backspace
> over that didn't do what it was su
On Sat, Jun 07, 2003 at 09:31:26PM +0200, Wouter Verhelst wrote:
> On Sat, Jun 07, 2003 at 04:21:33PM +0100, Colin Watson wrote:
> > What do you lose here? Those who have fonts that can display the
> > character in question will be able to do so; those who don't won't, but
> > will see some reasona
On Sat, Jun 07, 2003 at 12:01:49PM -0400, Colin Walters wrote:
> On Sat, 2003-06-07 at 09:59, Dmitry Borodaenko wrote:
>
> > I am using KOI8-R terminal which can not display Latin-1 characters, and
> > it seems backward to me to mandate or even allow _usage_ of UTF-8 ahead
> > of getting it _suppo
On Sat, Jun 07, 2003 at 04:21:33PM +0100, Colin Watson wrote:
> What do you lose here? Those who have fonts that can display the
> character in question will be able to do so; those who don't won't, but
> will see some reasonably obvious indicator like a "?" or a filled-in
> square to show that the
On Sat, 2003-06-07 at 13:43, Dmitry Borodaenko wrote:
> I don't see it as a proper credit to your contributors if their name
> appears as 'J?rg?n' (or even '' in case of Kanji) on my display.
That's a problem with your display.
> What I objected to is that they may: I'd rather they may not.
On Sat, Jun 07, 2003 at 04:21:33PM +0100, Colin Watson wrote:
DB>> I am using KOI8-R terminal which can not display Latin-1
DB>> characters,
CW> Where did Latin-1 come into this?
I said characters, not encoding, and I mean that KOI8-R character set
does not include characters from Latin-1. Ther
On Sat, 2003-06-07 at 09:59, Dmitry Borodaenko wrote:
> I am using KOI8-R terminal which can not display Latin-1 characters, and
> it seems backward to me to mandate or even allow _usage_ of UTF-8 ahead
> of getting it _supported_ across the system.
A growing amount of software in Debian has UTF
On Sat, Jun 07, 2003 at 04:59:29PM +0300, Dmitry Borodaenko wrote:
> On Thu, Jun 05, 2003 at 08:57:06PM -0400, Colin Walters wrote:
> JR>> the only thing that will change is that if someone complains at
> JR>> people who use UTF-8 in changelogs, a new retort will be
> JR>> available, "THE POLICY
On Thu, Jun 05, 2003 at 08:57:06PM -0400, Colin Walters wrote:
JR>> the only thing that will change is that if someone complains at
JR>> people who use UTF-8 in changelogs, a new retort will be
JR>> available, "THE POLICY MADE ME DO IT!!1!", or similar.
CW> Why would someone complain?
I would
On Fri, 2003-06-06 at 12:37, Bill Allombert wrote:
> 1) Changelog are required to be written in english, so non 7bit
> characters should be rare, and use of non latin-1 characters are
> probably not a good idea. For example, writing the name of a
> developer with japanese characters might cause
On Fri, Jun 06, 2003 at 06:37:11PM +0200, Bill Allombert wrote:
> On Fri, Jun 06, 2003 at 01:17:00PM +0200, Jérôme Marant wrote:
> > > I don't see all those (7|8)-bit-charset-using people requiring the
> > > same...
> > Policy would mean all of them in the same charset, UTF-8 that is.
> The iss
On Fri, Jun 06, 2003 at 01:17:00PM +0200, Jérôme Marant wrote:
> > I don't see all those (7|8)-bit-charset-using people requiring the
> > same...
>
> Policy would mean all of them in the same charset, UTF-8 that is.
The issue call for two comments:
1) Changelog are required to be written in en
En réponse à Josip Rodin <[EMAIL PROTECTED]>:
> On Thu, Jun 05, 2003 at 01:35:38PM +0200, Jérôme Marant wrote:
> > I've seen some UTF-8-encoded debian/changelog files but I haven't
> > seen anything mentioning it is allowed in Debian Policy.
> >
> > According to #174982, the proposal has be
On Thu, 2003-06-05 at 16:40, Josip Rodin wrote:
> On Thu, Jun 05, 2003 at 02:58:12PM -0400, Colin Walters wrote:
> > The problem is that we have no way to know what encoding an individual
> > Debian Changelog entry is in.
>
> The problem is that my point entirely flew over your head. The point was
On Thu, Jun 05, 2003 at 10:40:07PM +0200, Josip Rodin wrote:
> On Thu, Jun 05, 2003 at 02:58:12PM -0400, Colin Walters wrote:
> > The problem is that we have no way to know what encoding an individual
> > Debian Changelog entry is in.
> The problem is that my point entirely flew over your head. Th
On Thu, Jun 05, 2003 at 02:58:12PM -0400, Colin Walters wrote:
> The problem is that we have no way to know what encoding an individual
> Debian Changelog entry is in.
The problem is that my point entirely flew over your head. The point was,
as usual, that Policy is not designed to be a stick to b
On Thu, 2003-06-05 at 08:23, Josip Rodin wrote:
> Ahm. You need it written in the Policy manual to use a 16-bit charset?
As Steve points out, the size of the code space isn't particularly
relevant.
> I don't see all those (7|8)-bit-charset-using people requiring the same...
The problem is that
On Thu, Jun 05, 2003 at 02:23:36PM +0200, Josip Rodin wrote:
> On Thu, Jun 05, 2003 at 01:35:38PM +0200, Jérôme Marant wrote:
> > I've seen some UTF-8-encoded debian/changelog files but I haven't
> > seen anything mentioning it is allowed in Debian Policy.
> >
> > According to #174982, the p
On Thu, Jun 05, 2003 at 01:35:38PM +0200, Jérôme Marant wrote:
> I've seen some UTF-8-encoded debian/changelog files but I haven't
> seen anything mentioning it is allowed in Debian Policy.
>
> According to #174982, the proposal has been accepted but the bug
> is still open. When is this p
Hi,
I've seen some UTF-8-encoded debian/changelog files but I haven't
seen anything mentioning it is allowed in Debian Policy.
According to #174982, the proposal has been accepted but the bug
is still open. When is this planned for?
Thanks.
--
Jérôme Marant
26 matches
Mail list logo
