I would like to have some currency accent (I call it ||), for example || + s -> $, || + e -> €, y -> ¥ etc. I think a new keysym would have to be invented, I would prefer dead_currency as a name for it. I could make the lines for the compose map, but I don`t know how to tie things together neither how to make a patch. What do you think about it? Fabian.
Interesting idea, actually. As a first approach, I would do the following: pick one of existing dead_* keys, tried to add it to /usr/share/X11/locale/.../Compose into a sequence and see the whole chain working (I think it should, why would not it). Then I'd approach xorg maintainers to add dead_currency to keysymdef.h (in xorg maillist). I love the whole idea, so I can do the second part if you like.
OK I`ll try to get something out of <dead_abovering><s> etc. (actually this would make a bunch of <multi_key> combinations easier to press) But I have not yet understood the file structure. Just pasting into one of the variety of Compose files didn`t work straight away. Maybe only one of them is active on my system. Do I have to restart the X server or compile something etc.? If I succeed, I can only map these combinations on latin letters. I don`t know for example which hebrew letter the new shequel symbol of Israel should be put on. (Is it the current currency, by the way?) So people would be needed for hebrew, arabic, and cyrillic. Greetings, Fabian
Bugzilla Upgrade Mass Bug Change NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO. - benjsc fd.o Wrangler
Fabian, any success?
(In reply to comment #4) > Fabian, any success? > dead_currency has been added to http://cgit.freedesktop.org/xorg/proto/x11proto/tree/keysymdef.h#n418 along with compose sequences in the en_US.UTF-8 compose file.
So, I guess it can be safely closed.
I agree in closing this bug.
Thanks for the hint concerning dead_currency, Simos Xenitellis.
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.