On Tue, 2003-01-14 at 22:28, Junichi Uekawa wrote:
> The point is, we have working "iconv", and
> changing changelog will work.
Yep, definitely.
> man may need some hacking or other, I am not sure.
I hear the other Colin is on the job :)
> Not all of the statements made in that thread are not
> > Sorry, we have to start somewhere. Unicode is the way of the future,
> > and if we wait until every vendor of some random terminal updates it
> > with support for UTF-8, we will never start.
>
> I don't disagree that we should move to Unicode. I disagree that such
> a move must inherently
> > But the current situation is *already* broken! For example, for a
> > Chinese person, an ISO-8859-1 system simply cannot encode, nor display,
> > their language. I am aware that for people entrenched in legacy
> > charsets like ISO-8859-1, the transition may introduce
> > incompatibilities.
>Moreover, say the system administrator does something like 'find
>/home'. The resulting stream will be a mixture of ISO-8859-X and BIG5,
>and impossible to reliably differentiate.
And? A POSIX filename is not a string of characters, it's a string
of bytes. You have no technical need to differ
>1) A multiuser machine, with users using different charsets.
> Who decides which one is "local"?
>
>2) The sysamin/user changes the charset, e.g. from iso-8859-1
> to iso-8859-15 to get the Euro character.
> How should the filenames stay in the local charset when
> this changes? Would the
Today, I almost ran out of space on my /usr(2 gig partition). So, when trying
to find things to remove, I turned my attention to /usr/share/doc(which
contained 380 megs).
In doing this, I found several packages that had large quantities of
documentation in a non-doc type package. This meant that
On Tue, 2003-01-14 at 02:23, [EMAIL PROTECTED] wrote:
> Not acceptable. Filenames are and must be in the locale charset.
> There is no other sane option [...]
Heh. I will quote from a previous message of mine about filenames in
the locale charset, which, since you joined the discussion later, y
Adrian Bunk (2003-01-13 12:00:31 +0100) :
> I'm therefore suggesting that you change your policy to something like:
>
> <-- snip -->
>
> ...
> 2.3.9.1. Prompting in maintainer scripts
>
>
> Package maintainer scripts may prompt the user if necessary.
Hello Lars,
On Tue, Jan 14, 2003 at 12:30:28PM +0200, Lars Wirzenius wrote:
> ti, 14-01-2003 kello 10:23, Jochen Voss kirjoitti:
> > On Tue, Jan 14, 2003 at 01:23:51AM -0600, [EMAIL PROTECTED] wrote:
> > > Not acceptable. Filenames are and must be in the locale charset. There is
> > > no other san
ti, 14-01-2003 kello 10:23, Jochen Voss kirjoitti:
> On Tue, Jan 14, 2003 at 01:23:51AM -0600, [EMAIL PROTECTED] wrote:
> > Not acceptable. Filenames are and must be in the locale charset. There is
> > no other sane option [...]
> No, this does not work, too. Imagine two scenarios:
3) Floppies, C
Hello,
On Tue, Jan 14, 2003 at 01:23:51AM -0600, [EMAIL PROTECTED] wrote:
> Not acceptable. Filenames are and must be in the locale charset. There is
> no other sane option [...]
No, this does not work, too. Imagine two scenarios:
1) A multiuser machine, with users using different charsets.
W
>But what if the program *knows* the data is UTF-8 internally? Like all
>GNOME programs do, and my patch for dpkg tries to do?
Then it should be easy to convert it. You can't not convert and expect a
reasonable response - among other things, innocent UTF-8 characters can
include C1 bytes, and scr
13 matches
Mail list logo
