Re: Bug#436923: psili/dasia problem (Aarghhh!)

2007-10-20 Thread James Cloos
 Αλέξανδρος == Αλέξανδρος Διαμαντίδης [EMAIL PROTECTED] writes:

Αλέξανδρος Fortunately, 6 weeks ago, definitions for new keysyms for
Αλέξανδρος psili and dasia were commited to X: (thanks to James Cloos)

Αλέξανδρος xproto-7.0.11 which contains this change hasn't been
Αλέξανδρος released yet,

I pushed out the 7.0.11 release back on September 8:

http://xorg.freedesktop.org/archive/individual/proto/xproto-7.0.11.tar.gz
http://xorg.freedesktop.org/archive/individual/proto/xproto-7.0.11.tar.bz2

But it was not in time to be part of the katamari release.  Hopefully
distributions have picked it up, though.

Αλέξανδρος but after it is and the new keysyms start being used,
Αλέξανδρος this will be fixed once and for all...

With xproto-7.0.11 (for the key syms), current xlib (for the Compose file)
and current xkeyboard-symbols (for the XKB data) it should all work.

-JimC
-- 
James Cloos [EMAIL PROTECTED] OpenPGP: 1024D/ED7DAEA6

--
Linux-UTF8:   i18n of Linux on all levels
Archive:  http://mail.nl.linux.org/linux-utf8/



Re: Experiments with classical Greek keyboard input

2006-01-14 Thread James Cloos
 Jan == Jan Willem Stumpel [EMAIL PROTECTED] writes:

Jan setxkbmap gr(polytonic)+level3(lwin_switch)

Jan It should be possible to change from the default keyboard to classical
Jan Greek (and back) by some hotkey instead of a setxkbmap command.

You can accomplish that part by specifying multiple keymaps on the
setxkbmap line.

I use this command for my standard setup:

setxkbmap -layout us,el,ru,il -variant ,,phonetic,phonetic \
  -option ctrl:nocaps -option grp_led:scroll \
  -option compose:menu -option grp:ctrls_toggle \
  -option altwin:super_win

that gives me four layouts (the max that can be set at any given time)
which I can scroll through by pressing both control keys together (
that is the grp:ctrls_toggle option).  When I am in anything other
than the us map the scroll lock led is on (the grp_led:scroll option).
I also have the cap lock key be a control key and the menu key a
compose key.

Or at least I used to.  el no longer works for me.  

(The goal was to cover Latin/Greek/Cyrillic; I thru il in as well just
cause I could)

I also lack a good key to waste as a level3 key.  (The laptop lacks a
right win key¹ and I use the left win key for icewm.)

-JimC

¹ In fact the Fn key plus the left win key generates the keycode of
  the right win key, but it cannot be used as a modifyier because
  non-Fn-special keys are ignored when holding down Fn

-- 
James H. Cloos, Jr. [EMAIL PROTECTED]

--
Linux-UTF8:   i18n of Linux on all levels
Archive:  http://mail.nl.linux.org/linux-utf8/



Re: weird representation for FFFD

2005-07-06 Thread James Cloos
 Nicolas == Nicolas Mailhot [EMAIL PROTECTED] writes:

Nicolas dejavu just made it in fedora extras. Does it have the same
Nicolas problem ?  (if the answer is yes the dejavu people seem to
Nicolas fix their fonts pretty fast - just make them release a fixed
Nicolas version and I'll respin the dejavu package)

Inspired by this thread I've started on U+FFFD glyphs for deja.

-JimC
-- 
James H. Cloos, Jr. [EMAIL PROTECTED] http://jhcloos.com

--
Linux-UTF8:   i18n of Linux on all levels
Archive:  http://mail.nl.linux.org/linux-utf8/



Re: Weird behaviour of emacs

2005-02-12 Thread James Cloos
 David == David Sumbler [EMAIL PROTECTED] writes:

David If I save the file in emacs-mule format, a lower case 'alpha'
David appears as bytes [92 a6 c1] in case (a), and [9c f4 a7 b1] in
David case (b).  Other characters show similar differences.

Given that your file is in 2022-JP, the correct behavior according to
the unicode standard is to convert any greek or cyrillic in it to the
wide compatability chars rather than normal greek or cyrillic chars.

This is an artifact of unicode's round-trip guarantee for legacy char
sets and the inclusion of wide greek and cyrillic in the legacy cjk
character standards.

Ensuring font support for both ranges is a bit of a pain.  You'll
have to play around with fontsets to get both ranges to display in
the gui.  For the terminal you'll need to have it use a font that
covers both.  (Generally it will use one font for narrow and another
for wide, it shouldn't be too hard to find a couple that work well
together and that have enough coverage.  As an example, the 9x18 and
18x18 bdf fonts should do it.)  If you are using a terminal app that
uses like gnome-terminal Pango () it will use a substitute font
for any missing glyphs.

-JimC
-- 
James H. Cloos, Jr. [EMAIL PROTECTED]


--
Linux-UTF8:   i18n of Linux on all levels
Archive:  http://mail.nl.linux.org/linux-utf8/