Cesar Eduardo Barros wrote:
> I think debconf should use UTF-8 for the templates and recode on the fly.
Well, if you send in a patch, I will consider it.
> There's nothing worse than having gibberish in ten different charsets in the
> same template file.
This is why the template file is the "com
Fumitoshi UKAI wrote:
> debconf doesn't assume any encoding, does it?
> We're usually using EUC-JP charset for debconf.
No, debconf knows about as little about l10n and i18n as I.
I'm glad to hear the Japanese stuff works btw.
--
see shy jo
On Jun 01, Cesar Eduardo Barros <[EMAIL PROTECTED]> wrote:
>Ask the IETF. They seem to like UTF8 a lot.
Because it's ASCII-compatible. This is not relevant.
>Ask Linus too. The UTF8 support is in the kernel since, what, 2.0.x?
Because it's ASCII-compatibile. This is not relevant.
UTF-8 maybe b
On Thu, May 31, 2001 at 09:06:10PM +0200, Christian Kurz wrote:
> On 01-05-30 Cesar Eduardo Barros wrote:
> > Package: debian-policy
> > Version: 3.5.4.0
> > Severity: wishlist
> >
> > I think Debian should start to move into using UTF-8 by default everywhere.
>
> May I ask why we want to choose
On 01-05-30 Cesar Eduardo Barros wrote:
> Package: debian-policy
> Version: 3.5.4.0
> Severity: wishlist
>
> I think Debian should start to move into using UTF-8 by default everywhere.
May I ask why we want to choose UTF-8 instead of UTF-5 or UTF-16? And
why should we exactly switch to Unicode? H
Robert Bihlmeyer <[EMAIL PROTECTED]> wrote:
> Background:
> ldconfig has two purposes:
> 1. For each shared library, create/update a symbolic link from the
> library's soname to the library file. The link is only changed if
> it was broken/non-existing before, or the library in question has a
I propose that instead of calling "ldconfig", maintainer scripts of
packages containing shared libraries should call "ldconfig -X".
Background:
ldconfig has two purposes:
1. For each shared library, create/update a symbolic link from the
library's soname to the library file. The link is only ch
On Thu, May 31, 2001 at 11:18:38PM +0900, Fumitoshi UKAI wrote:
> > How do tools (eg. debconf) know what coding set to use when reading a
> > file (eg. templates file)? Or, is ISO-8859-1 assumed?
>
> debconf doesn't assume any encoding, does it?
> We're usually using EUC-JP charset for debconf.
>
Fumitoshi UKAI (2001-05-31 23:18:38 +0900) :
> AFAIK, emacsen could handle UTF-8 with mule-ucs package.
Yes. It works very well for me. It also supports UTF-7 and UTF-16,
by the way :-)
> If policy claims to make sure everything works with UTF-8 charset,
> should mule-ucs be merged into each
At 31 May 2001 14:04:39 +1000,
Brian May wrote:
> > "Cesar" == Cesar Eduardo Barros <[EMAIL PROTECTED]> writes:
>
> Cesar> - Making sure everything works with UTF-8 charset
>
> Biggest problem for me, here (unless that has changed in the past
> month or so) is xemacs. Probably the same f
Seconded.
--
Raul
On Thu, May 31, 2001 at 07:36:39PM +1000, Brendan O'Dea wrote:
> Perhaps it would be clearer to just explicitly indicate the source of
> %Config inline:
>
> --- perl-policy.sgml.orig Thu May 31 19:34:40 2001
> +++ perl-policy.sgml Thu May 31 19:33:04 2001
> @@ -12,7 +12,7
On Fri, May 25, 2001 at 02:51:29PM -0400, Raul Miller wrote:
>Package: debian-policy
>Version: 3.5.4.0
>Severity: wishlist
Perhaps it would be clearer to just explicitly indicate the source of
%Config inline:
--- perl-policy.sgml.orig Thu May 31 19:34:40 2001
+++ perl-policy.sgmlThu May
12 matches
Mail list logo
