Your message dated Wed, 16 Feb 2005 11:57:09 -0800 (PST)
with message-id <[EMAIL PROTECTED]>
and subject line Bug#295389: kwrite, kate: does not open UTF-8 file as UTF-8
(need to manually remove config file)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 15 Feb 2005 14:53:02 +0000
>From [EMAIL PROTECTED] Tue Feb 15 06:53:02 2005
Return-path: <[EMAIL PROTECTED]>
Received: from web60206.mail.yahoo.com [216.109.118.101]
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1D144U-0003aq-00; Tue, 15 Feb 2005 06:53:02 -0800
Received: (qmail 97919 invoked by uid 60001); 15 Feb 2005 14:52:27 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=s1024; d=yahoo.com;
b=MZ2WnVLNGeCSbr7HvSBakyTaL9VtJ0hkcSFUnhE899jtlKbxslNp24/DXhrxRM2sMPRXKCaFHrOSRYI6gKgFwtDi92AVlTgQuiwxjrzNyI/9B5T7lL/E1jwyfUbRXC+p1EjXOPxbQX5Kpcrxpg0Gif+IsDYQF7oKsqnPr3sTjoc=
;
Message-ID: <[EMAIL PROTECTED]>
Received: from [209.5.96.158] by web60206.mail.yahoo.com via HTTP; Tue, 15 Feb
2005 06:52:27 PST
Date: Tue, 15 Feb 2005 06:52:27 -0800 (PST)
From: Ricky Ng-Adam <[EMAIL PROTECTED]>
Subject: kwrite, kate: does not open UTF-8 file as UTF-8 (need to manually
remove config file)
To: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: kate
Version: 4:3.3.2-1
Severity: important
Tags: l10n
0) changed system locale with `dpkg-reconfigure locales` from
en_US.ISO8859-1 to ca_EN.UTF-8
1) created a text file with accented characters:
éééééééé
2) verified that this is an UTF-8 using `file`
[EMAIL PROTECTED]:~$ file eacute-utf8.txt
eacute-utf8.txt: UTF-8 Unicode text
3) notice that the output is incorrect when opening UTF-8 file with
kwrite and kate:
ééééééééé
4) With the File > Open dialog, I can see at the top right that the
editor currently expects iso8859-1 files
5) if I just start the kwrite, File > Open also expects iso8859-1
instead of utf-8
6) The config file for kwrite contains the line `Encoding=ISO 8859-1`.
Deleting the file ~/.kde/share/config/kwriterc corrects the problem.
7) more:
share/apps/kate/metainfos:Encoding=ISO 8859-1
share/apps/kate/metainfos:Encoding=ISO 8859-1
share/config/katerc:Encoding=ISO 8859-1
share/config/kilerc:Encoding=ISO 8859-1
share/config/quantarc:Default encoding=ISO 8859-1
Should it be necessary to manually delete the file? Why does it keep an
Encoding directive?
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.10.mt-m8305-42u
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Versions of packages kate depends on:
ii kdelibs4 4:3.3.2-1 KDE core libraries
ii libart-2.0-2 2.3.17-1 Library of functions for
2D graphi
ii libc6 2.3.2.ds1-20 GNU C Library: Shared
libraries an
ii libfam0c102 2.7.0-6 client library to control
the FAM
ii libgcc1 1:3.4.3-6 GCC support library
ii libice6 4.3.0.dfsg.1-10 Inter-Client Exchange
library
ii libidn11 0.5.2-3 GNU libidn library,
implementation
ii libpng12-0 1.2.8rel-1 PNG library - runtime
ii libqt3c102-mt 3:3.3.3-8 Qt GUI Library (Threaded
runtime v
ii libsm6 4.3.0.dfsg.1-10 X Window System Session
Management
ii libstdc++5 1:3.3.5-5 The GNU Standard C++
Library v3
ii libx11-6 4.3.0.dfsg.1-10 X Window System protocol
client li
ii libxext6 4.3.0.dfsg.1-10 X Window System
miscellaneous exte
ii libxrender1 0.8.3-7 X Rendering Extension
client libra
ii xlibs 4.3.0.dfsg.1-10 X Keyboard Extension (XKB)
configu
ii zlib1g 1:1.2.2-3 compression library -
runtime
-- no debconf information
__________________________________
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com
---------------------------------------
Received: (at 295389-done) by bugs.debian.org; 16 Feb 2005 19:57:40 +0000
>From [EMAIL PROTECTED] Wed Feb 16 11:57:40 2005
Return-path: <[EMAIL PROTECTED]>
Received: from web60202.mail.yahoo.com [216.109.118.97]
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1D1VIp-0002E7-00; Wed, 16 Feb 2005 11:57:39 -0800
Received: (qmail 17468 invoked by uid 60001); 16 Feb 2005 19:57:09 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=s1024; d=yahoo.com;
b=Zla1wlzE2KOFXJein97/WzqFxiJo1lC/LPP5xi/bkZ32FWVVF/GA0D+qp1y25SB2/uAGHzg6vIE74PfNGHE+6J9vWr/GF1MLBctOtG/ndoVSweRY2R8BCs/EeO0S8hici5rzrgus4SstEq95Zze3rlUCkR4jYVvXSq3Ohtnt5o4=
;
Message-ID: <[EMAIL PROTECTED]>
Received: from [209.5.96.158] by web60202.mail.yahoo.com via HTTP; Wed, 16 Feb
2005 11:57:09 PST
Date: Wed, 16 Feb 2005 11:57:09 -0800 (PST)
From: Ricky Ng-Adam <[EMAIL PROTECTED]>
Subject: Re: Bug#295389: kwrite, kate: does not open UTF-8 file as UTF-8 (need
to manually remove config file)
To: Zsolt Rizsanyi <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
In-Reply-To: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.1 required=4.0 tests=BAYES_44,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Hello!
--- Zsolt Rizsanyi <[EMAIL PROTECTED]> wrote:
> I didn't check it for others but eg. in kate you can set the desired
> encoding value by View|Set Encoding. If you set that to Auto then it
> should be able to open your file. The default value is Auto. If you
> set it
> to some other value, then you expect all the files you open to be of
> that
> encoding.
> How did your setting end up as ISO 8859-1 instead of Auto I don't
> know. If
> I remember correctly then long ago kate did not have setting for auto
Thanks for clarifying this. I'm guessing anyway that this situation
should not occur very often - few users will switch from one locale to
the other. But it does make it harder to push everyone toward UTF-8...
Thanks!
Ricky
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
