On Sun, 2003-01-05 at 22:00, Richard Braakman wrote:
> On Sun, Jan 05, 2003 at 09:12:36PM -0500, Colin Walters wrote:
> > However, if these programs display
> > them to the user on a tty, it will be necessary to convert them to the
> > user's locale encoding
>
> Hmm. Remember the far more common
On Sun, Jan 05, 2003 at 09:12:36PM -0500, Colin Walters wrote:
> However, if these programs display
> them to the user on a tty, it will be necessary to convert them to the
> user's locale encoding
Hmm. Remember the far more common case of a program that takes a
filename on the command line and
On Sun, 2003-01-05 at 15:13, Denis Barbier wrote:
> Consider a program written in C, which creates new files with open(2);
> if I understand your proposal right, when a filename is not UTF-8
> encoded, it should be converted into UTF-8 according to user's locale.
Well, broadly speaking, there are
On Sun, Jan 05, 2003 at 01:41:47PM -0500, Colin Walters wrote:
> On Sun, 2003-01-05 at 11:07, Michael Bramer wrote:
>
> > The DDTP has no problmes with UTF-8 in control fields. Some maintainer
> > use UTF-8 or something else with 'some translations' in the descriptions.
> >
> > This is not nice.
Hi
On Sat, Jan 04, 2003 at 07:21:11PM -0600, Jamin W. Collins wrote:
> A while back, on one of my other lists, there was a discussion about
> user configuration files for the program and where to put them. That
> led to how frustrated many users were with the dot files just littering
> their home
On Sun, Jan 05, 2003 at 12:09:09PM -0500, Colin Walters wrote:
> On Sun, 2003-01-05 at 09:23, Denis Barbier wrote:
> > On Sat, Jan 04, 2003 at 12:10:42PM -0500, Colin Walters wrote:
> > [...]
> > > What *is* debatable is when and how to make the transition, which is
> > > what we're doing now.
> >
On Sun, 2003-01-05 at 11:07, Michael Bramer wrote:
> The DDTP has no problmes with UTF-8 in control fields. Some maintainer
> use UTF-8 or something else with 'some translations' in the descriptions.
>
> This is not nice.
>
> The policy should be: use normal ACSII and UTF-8 encoding if you use
On Sun, Jan 05, 2003 at 02:36:16AM -0500, Colin Walters wrote:
> [ CC'd to the Debian Description Translation Project maintainer, as he
> may be interested ]
thanks
> On Fri, 2003-01-03 at 13:24, Colin Walters wrote:
> > On Fri, 2003-01-03 at 11:45, Radovan Garabik wrote:
> >
> > > > #99933 goes
On Sun, Jan 05, 2003 at 04:30:48AM +0100, Marco d'Itri wrote:
> Recent programs do not have user-editable configuration files anyway.
Parse error.
--
2. That which causes joy or happiness.
On Sun, Jan 05, 2003 at 01:08:45PM +0200, Lars Wirzenius wrote:
> Still speaking as a user, I'm not annoyed by a dotfile per program I
> use. I'm much more annoyed by all the useless dotfiles, created by
> programs that I run once, and never again, without even having saved a
> configuration, or do
On Sun, 2003-01-05 at 09:23, Denis Barbier wrote:
> On Sat, Jan 04, 2003 at 12:10:42PM -0500, Colin Walters wrote:
> [...]
> > What *is* debatable is when and how to make the transition, which is
> > what we're doing now.
> [...]
>
> So how to implement your proposal?
> The main issue is to patch
On Sun, 2003-01-05 at 08:05, Sebastian Rittau wrote:
> (Evolution is bad enough by creating an "evolution" directory in my
> homne [...]
The reason it does this is because evolution's directory isn't just
configuration files; it also contains all your mail. Having your mail
hidden away in a . d
On Sat, Jan 04, 2003 at 12:10:42PM -0500, Colin Walters wrote:
[...]
> What *is* debatable is when and how to make the transition, which is
> what we're doing now.
[...]
So how to implement your proposal?
The main issue is to patch glibc API so that filenames are supposed
to be UTF-8 encoded. Has
On Sun, Jan 05, 2003 at 01:08:45PM +0200, Lars Wirzenius wrote:
> su, 05-01-2003 kello 03:21, Jamin W. Collins kirjoitti:
> > So, what do you folks think? Would it be worth while to have a Debian
> > policy regarding the placement of user configuration files in a
> > configuration sub directory of
On Sun, Jan 05, 2003 at 02:37:07AM +, Julian Gilbey wrote:
> I like the idea. I vote for ~/etc, though, not ~/.etc; there's little
> point hiding this one directory name if it is going to contain all of
> the configuration data.
While the general idea of having all configuration files in one
* Colin Walters
| On Sat, 2003-01-04 at 19:22, Tollef Fog Heen wrote:
|
| > And any hard coded scripts using -d norsk (or -d bokmal) for getting
| > Norwegian ispell output.
|
| Hm, but if the filename is already UTF-8, what is the problem?
It isn't in stable, which means that I want to keep co
su, 05-01-2003 kello 03:21, Jamin W. Collins kirjoitti:
> So, what do you folks think? Would it be worth while to have a Debian
> policy regarding the placement of user configuration files in a
> configuration sub directory of the user's home dir?
Speaking as a user, I'd hate this change. It woul
On Sun, 5 Jan 2003 05:30:46 -0500
David B Harris <[EMAIL PROTECTED]> wrote:
> As for you leaving Debian ... why do people always bring that out?
> Jeeze.
Just to clarify. One can assume that if Debian Policy starts mandating
things without merit and which cause our users problems, then users will
On Sun, 5 Jan 2003 03:28:40 +
Colin Watson <[EMAIL PROTECTED]> wrote:
> In other words, somebody will be told "that bug's fixed in the
> development version of this package upstream", so they go and try it
> out. But, hey presto, not only does it ignore the configuration set up
> while using th
On Sun, 5 Jan 2003 04:30:48 +0100
Marco d'Itri <[EMAIL PROTECTED]> wrote:
> >Maybe ask on the FHS list for comments, too?
> This is outside FHS-domain. But I think that a so big change from
> standard UNIX practice would be so stupid that if accepted I would
> probably leave debian.
It's been sta
[ CC'd to the Debian Description Translation Project maintainer, as he
may be interested ]
On Fri, 2003-01-03 at 13:24, Colin Walters wrote:
> On Fri, 2003-01-03 at 11:45, Radovan Garabik wrote:
>
> > > #99933 goes a lot farther than #174982. First of all, we can't even
> > > suggest that people
21 matches
Mail list logo