Autokey fails to send special characters

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Creating phrase with special characters (I used ◕ ◡ ◕)
2.Trying to use the phrase
3.

What is the expected output? What do you see instead?
I was hoping I could phrasebind ◕ ◡ ◕ so I didn't have to copy it from
somewhere or set up text filters on xchat and pidgin but when I tried to
invoke the phrase, it didn't send the special characters, only the spaces

What version of the product are you using? On what operating system?
Version 0.70.4-1 on Arch Linux

Please provide any additional information below.
N/A

Original issue reported on code.google.com by sogemp...@gmail.com on 18 May 2010 at 6:00

[GoogleCodeExporter]

Please follow the directions on the Troubleshooting wiki page - at the very top 
it
explains how to produce a debug log.

Original comment by cdekter on 19 May 2010 at 10:06

[GoogleCodeExporter]

DEBUG - service - Key: h
DEBUG - service - Input stack at end of handle_keypress: [u'h']
DEBUG - service - Key: h
DEBUG - service - Input stack at end of handle_keypress: [u'h', u'h']
DEBUG - service - Key: e
DEBUG - service - Input stack at end of handle_keypress: [u'h', u'h', u'e']
DEBUG - service - Key: e
DEBUG - service - Input stack at end of handle_keypress: [u'h', u'h', u'e', 
u'e']
DEBUG - service - Key: l
DEBUG - service - Input stack at end of handle_keypress: [u'h', u'h', u'e', 
u'e', u'l']
DEBUG - service - Key: s
DEBUG - interface - Send special key: ['<backspace>']
DEBUG - interface - Send special key: ['<backspace>']
DEBUG - interface - Send special key: ['<backspace>']
DEBUG - interface - Send special key: ['<backspace>']
DEBUG - interface - Send special key: ['<backspace>']
DEBUG - interface - Send special key: ['<backspace>']
DEBUG - iomediator - Send via event interface
DEBUG - interface - Sending string: u'\u25d5 \u25e1 \u25d5'
DEBUG - service - Input stack at end of handle_keypress: []

Original comment by sogemp...@gmail.com on 19 May 2010 at 10:12

[GoogleCodeExporter]

I don't know those characters don't get typed, as other unicode characters do 
work. I
suspect they might be outside the range that X allows to be mapped. You can get 
it
working by using the Clipboard send mode instead of Keyboard.

Original comment by cdekter on 21 May 2010 at 3:19

• Changed state: WontFix