Your message dated Mon, 27 Sep 2004 20:19:25 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#267062: xlibs: [xkb] wrong Compose file for pl_PL.UTF-8?
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; 20 Aug 2004 13:31:27 +0000
>From [EMAIL PROTECTED] Fri Aug 20 06:31:26 2004
Return-path: <[EMAIL PROTECTED]>
Received: from chastell.shot.pl [80.55.253.30]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1By9UM-0004Z3-00; Fri, 20 Aug 2004 06:31:26 -0700
Received: by chastell.shot.pl (Postfix, from userid 1000)
id 4FBCB3917E; Fri, 20 Aug 2004 15:31:24 +0200 (CEST)
Date: Fri, 20 Aug 2004 15:31:24 +0200
From: Shot <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: xlibs: [xkb] wrong Compose file for pl_PL.UTF-8?
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
X-Reportbug-Version: 2.64
Organization: Freelance Shooters
X-Operating-System: Debian GNU/Linux, up 35 days, 17:25
User-Agent: Mutt/1.5.6+20040722i
Content-Transfer-Encoding: quoted-printable
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(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_2004_03_25
X-Spam-Level:
Package: xlibs
Version: 4.3.0.dfsg.1-6
Severity: normal
Hello.
I'm using pl_PL.UTF-8 locale, and would like to be able to type certain
characters, like em- and en-dashes, "curly" quotes, ellipsis, etc.
I've found out that these characters should be easily obtainable with
the compose key, and it seems they are in fact defined properly:
[EMAIL PROTECTED]:~$ grep pl /usr/X11R6/lib/X11/locale/compose.dir
iso8859-2/Compose pl_PL.ISO8859-2
en_US.UTF-8/Compose pl_PL.UTF-8
iso8859-2/Compose: pl_PL.ISO8859-2
en_US.UTF-8/Compose: pl_PL.UTF-8
[EMAIL PROTECTED]:~$ grep DASH /usr/X11R6/lib/X11/locale/en_US.UTF-8/Compose
<Multi_key> <minus> <minus> <period> : "=E2=80=93" U2013 # EN DASH
<Multi_key> <minus> <minus> <minus> : "=E2=80=94" U2014 # EM DASH
Yet when I try to input <Multi_key> <minus> <minus> <period> I get
the hyphen character right after the second <minus>; it seems that
X is using the iso8859-2/Compose mapping instead of en_US.UTF-8/Compose:
[EMAIL PROTECTED]:~$ grep "<minus> <minus>" /usr/X11R6/lib/X11/locale/iso8859-2=
/Compose
<Multi_key> <minus> <minus> : "\255" hyphen
Additionally, the <Multi_key> <a> <comma> sequence inputs aogonek, so
I'm either using ISO-8859-2, -4 or -13 mappings (I'm betting on -2):
[EMAIL PROTECTED]:~$ grep -r "<a> <comma>" /usr/X11R6/lib/X11/locale/
/usr/X11R6/lib/X11/locale/iso8859-13/Compose:<Multi_key> <a> <comma> =
: "\340" aogonek
/usr/X11R6/lib/X11/locale/iso8859-2/Compose:<Multi_key> <a> <comma> =
: "\261" aogonek
/usr/X11R6/lib/X11/locale/iso8859-4/Compose:<Multi_key> <a> <comma> =
: "\261" aogonek
Is there a way to set X to use the en_US.UTF-8/Compose mappings?
Shouldn't this be the default source for pl_PL.UTF-8 locale?
(I tried overwriting iso8859-2/Compose with en_US.UTF-8/Compose and it
didn't change anything, so I guess the compose mappings must be defined
elsewhere as well.)
-- Package-specific info:
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.18-bf2.4
Locale: LANG=3Dpl_PL.UTF-8, LC_CTYPE=3Dpl_PL.UTF-8
Versions of packages xlibs depends on:
ii libice6 4.3.0.dfsg.1-6 Inter-Client Exchange librar=
y
ii libsm6 4.3.0.dfsg.1-6 X Window System Session Mana=
gement
ii libx11-6 4.3.0.dfsg.1-6 X Window System protocol cli=
ent li
ii libxext6 4.3.0.dfsg.1-6 X Window System miscellaneou=
s exte
ii libxft1 4.3.0.dfsg.1-6 FreeType-based font drawing =
librar
ii libxi6 4.3.0.dfsg.1-6 X Window System Input extens=
ion li
ii libxmu6 4.3.0.dfsg.1-6 X Window System miscellaneou=
s util
ii libxmuu1 4.3.0.dfsg.1-6 lightweight X Window System =
miscel
ii libxp6 4.3.0.dfsg.1-6 X Window System printing ext=
ension
ii libxpm4 4.3.0.dfsg.1-6 X pixmap library
ii libxrandr2 4.3.0.dfsg.1-6 X Window System Resize, Rota=
te and
ii libxt6 4.3.0.dfsg.1-6 X Toolkit Intrinsics
ii libxtrap6 4.3.0.dfsg.1-6 X Window System protocol-tra=
pping=20
ii libxtst6 4.3.0.dfsg.1-6 X Window System event record=
ing an
ii xlibs-data 4.3.0.dfsg.1-6 X Window System client data
-- no debconf information
Cheers,
-- Shot (Piotr Szotkowski)
--=20
I'm changing \accent to \mathaccent here; wish me luck.
~~~ TeX ~~~
http://shot.pl/hover=
craft/
---------------------------------------
Received: (at 267062-done) by bugs.debian.org; 28 Sep 2004 01:19:27 +0000
>From [EMAIL PROTECTED] Mon Sep 27 18:19:26 2004
Return-path: <[EMAIL PROTECTED]>
Received: from dhcp065-026-182-085.indy.rr.com (sisyphus.deadbeast.net)
[65.26.182.85]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CC6eM-0005Es-00; Mon, 27 Sep 2004 18:19:26 -0700
Received: by sisyphus.deadbeast.net (Postfix, from userid 1000)
id BE24968C013; Mon, 27 Sep 2004 20:19:25 -0500 (EST)
Date: Mon, 27 Sep 2004 20:19:25 -0500
From: Branden Robinson <[EMAIL PROTECTED]>
To: Jeff Licquia <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#267062: xlibs: [xkb] wrong Compose file for pl_PL.UTF-8?
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL
PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="5/uDoXvLw7AC5HRs"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.6+20040818i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-1.1 required=4.0 tests=BAYES_44,CLICK_BELOW,
HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
--5/uDoXvLw7AC5HRs
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Sep 26, 2004 at 11:31:38AM -0500, Jeff Licquia wrote:
> Sorry for the late reply; it appears that Debian's mail system held onto
> these messages for a while, so I just now got them.
Thanks for the explanation, Jeff; I'm quoting your message as justification
for closing the bug.
Closing as due to unfortunate choice of input method (a user configuration
issue).
Come to think of it...Jeff, do you mind if I use your reply as the basis
for a new entry in the Debian X FAQ[1]?
[1] http://necrotic.deadbeast.net/xsf/XFree86/trunk/debian/local/FAQ.xhtml
> GTK+ has its own input method framework that is separate from the X
> input methods. This is necessary because GTK+ is supposed to be
> independent of X.
>=20
> The default input method is, of course, Latin. When implementing this
> method, the GTK+ people focused on ISO-8859-1, and did not implement
> many of the other Latin character sets. This is why GTK-based programs
> seem not to be able to type characters that other pure X programs can.
>=20
> There are several things you can do about the problem. All of them
> involve using a different GTK+ input method. You can test these by
> opening some GTK+ app that takes input, such as gedit. Right-click on
> the edit box, and there should be a submenu for "Input Methods". The
> new input method should show up in that submenu.
>=20
> - Get a better GTK+ input method. The gtk-im-extra Sourceforge project
> (http://gtk-im-extra.sourceforge.net/) contains a Latin Plus input
> method, for example. While you're at it, you might also lobby the GTK+
> people to include gtk-im-extra, and make Latin Plus the default.
>=20
> - There are alternative input method projects out there that provide
> GTK+ IM shims; look for the packages iiimgcf, scim-gtk2-immodule, and
> uim-gtk2.0 in testing/unstable. Most of these, though, are aimed at
> non-Latin issues, so I can't tell you if any of them would be
> appropriate.
>=20
> - Additionally, GTK+ ships with a XIM shim module. This is the
> solution I've implemented.
>=20
> If you want to make some other input method the default, edit
> /etc/environment, and set the environment variable GTK_IM_MODULE there
> to the input method module you want ("xim" for the XIM shim). Of
> course, you can do the same thing for just yourself by setting that
> environment variable in .profile, .bashrc, or whatever.
--=20
G. Branden Robinson | Why should I allow that same God
Debian GNU/Linux | to tell me how to raise my kids,
[EMAIL PROTECTED] | who had to drown His own?
http://people.debian.org/~branden/ | -- Robert Green Ingersoll
--5/uDoXvLw7AC5HRs
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iEYEARECAAYFAkFYvB0ACgkQ6kxmHytGonzbTwCgpNj8nKnNY/qS0Y/owmfWkAXv
gHkAn1d8XciwOsPqF64PfifcyD96n5R6
=2Hn/
-----END PGP SIGNATURE-----
--5/uDoXvLw7AC5HRs--
