--nextPart11778391.hP0XhNXdz2
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
David Faure wrote:
>On Thursday 29 March 2007, Thiago Macieira wrote:
>> I know. I have to modify the XKB layout file every time I upgrade X so
>> that en_US also has the ISO-9993-1 secondary layout. (I also have to
>> modify the Compose file so that I get the "=C3=A7" I badly need)
>
> =C3=A7? No modification needed, I just do Compose , + c with the
> default en_US layout.
I need to produce "=C3=A7", not "=C4=87".
Some distributions come with two Compose files for UTF-8 locales: the=20
en_US.UTF-8 and the pt_BR.UTF-8 one. The latter is exactly like the=20
former, with that change. The former is used for all locales, except=20
pt_BR.UTF-8.
Somehow, that seems to get constantly broken on upgrade.
>> It's a function of your chosen keyboard layout, not of your keyboard.
>
>Of course. But we're talking about the default shortcuts in kde, and I'm
> just saying that most KDE users are not going to do the above steps, so
> you can't rely on AltGr being present for standard shortcuts.
Oh, no, I never meant that. AltGr cannot be used as a modifier for further=
=20
shortcuts. We can't do that because AltGr by itself might be necessary to=20
compose some of the shortcuts we do define.
=46or instance, Alt+@ in a Norwegian keyboard would be produced with=20
Alt+AltGr+2.
Maybe we should start using "Ctrl+=E2=82=AC", "Ctrl+Shift+=C3=B8" as shortc=
uts :-)
=2D-=20
=C2=A0 Thiago Macieira =C2=A0- =C2=A0thiago (AT) macieira.info - thiago (AT=
) kde.org
=C2=A0 =C2=A0 PGP/GPG: 0x6EF45358; fingerprint:
=C2=A0 =C2=A0 E067 918B B660 DBD1 105C =C2=A0966C 33F5 F005 6EF4 5358
--nextPart11778391.hP0XhNXdz2
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQBGDC5qM/XwBW70U1gRAj0mAJ9B6yvULd7suO5vVZdm26xNeAXyBgCfYfD7
vckK+u6yg15bBwtZSPiMBiM=
=vKEM
-----END PGP SIGNATURE-----
--nextPart11778391.hP0XhNXdz2--