Attachment 934 Details for Bug 1411 – Submitted correct /etc/X11/xkb/symbols/pc/mt

Submitted correct /etc/X11/xkb/symbols/pc/mt

mt (text/plain), 1.52 KB, created by Ramon Casha on 2004-09-18 09:39:13 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Ramon Casha

Created: 2004-09-18 09:39:13 UTC

Size: 1.52 KB

patch

obsolete

>// Maltese keyboard map (based on MSA Standard DMS100)
>// by Ramon Casha (ramon.casha@linux.org.mt)
>//
>// $XFree86: xc/programs/xkbcomp/symbols/pc/mt,v 1.3 2002/12/13 04:18:04 dawes Exp $
>
>partial default alphanumeric_keys
>xkb_symbols "basic" {
>
>    include "pc/latin"
>
>    name[Group1]="Maltese";
>
>    // The following four sets are the four additional letters, with the UK
>    // equivalents
>    key <TLDE>	{ [ cabovedot,  Cabovedot,        grave,      notsign ]	};
>    key <AD11>	{ [ gabovedot,  Gabovedot,  bracketleft,    braceleft ]	};
>    key <AD12>	{ [   hstroke,    Hstroke, bracketright,   braceright ]	};
>    key <LSGT>	{ [ zabovedot,  Zabovedot,    backslash,          bar ]	};
>
>    // Euro symbol
>    key <AE03>	{ [         3,   EuroSign,     sterling               ]	};
>
>    // Long accent
>    key <AE06>	{ [         6, asciicircum, dead_circumflex, dead_circumflex ]	};
>
>    // Normal accented vowels
>    key <AD03>	{ [         e,          E,       egrave,       Egrave ]	};
>    key <AD07>	{ [         u,          U,       ugrave,       Ugrave ]	};
>    key <AD08>	{ [         i,          I,       igrave,       Igrave ]	};
>    key <AD09>	{ [         o,          O,       ograve,       Ograve ]	};
>    key <AC01>	{ [         a,          A,       agrave,       Agrave ]	};
>
>    key <BKSL>	{ [numbersign, asciitilde,   dead_grave,   dead_breve ]	};
>    key <AE02>	{ [         2,   quotedbl,  twosuperior,    oneeighth ]	};
>    key <AC11>	{ [apostrophe,         at, dead_circumflex, dead_caron]	};
>
>    include "level3(ralt_switch_multikey)"
>};

Actions: View

Attachments on bug 1411: 934 | 5873

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.