Bug 19753

Summary: Hindi Wx input method
Product: xkeyboard-config Reporter: Bryce Harrington <bryce>
Component: GeneralAssignee: xkb
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium CC: panemade
Version: unspecifiedKeywords: NEEDINFO
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: in_wx_hindi

Description Bryce Harrington 2009-01-26 15:51:23 UTC
Created attachment 22259 [details]
in_wx_hindi

Forwarding this bug report from Ubuntu:
https://bugs.edge.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/274024

Here is the Hindi (Devanagari) Input system symbols file developed at IIIT-Hyderabad.
Comment 1 Sergey V. Udaltsov 2009-01-27 14:20:31 UTC
Will go in after release.
Comment 2 Sergey V. Udaltsov 2009-01-28 15:27:22 UTC
In symbols/in there is already "deva" section. What's the purpose and difference of this one? Some background would be nice to have.

What would be the proper id for it in symbols/in (of course, not "basic")? Proper name? ("India - ????"). Thanks
Comment 3 Bryce Harrington 2009-02-04 20:26:08 UTC
User replies on LP bug:

"WX notation is a phonetic keyboard layout for hindi, it is easier than the standard Hindi (Deva )

http://mirror.umoss.org/mozdev/indicime/wx_keyboard.html"
Comment 4 Sergey V. Udaltsov 2009-02-05 15:07:31 UTC
Committed, thanks! in(hin-wx)
Comment 5 Parag 2009-06-23 03:10:27 UTC
Where can I find unicode/hex value for dead_V? dead_V is added to English letter "V".
Comment 6 Parag 2009-08-20 22:15:30 UTC
opening this as we need to fix dead_V I guess.
Comment 7 Sergey V. Udaltsov 2009-08-21 02:47:52 UTC
Could you please explain me, what is "dead v"? How would you use it as a deadkey?

In /usr/share/X11/locale/*/Compose files I do not see any reference to dead_v, it means currently no Compose sequences are using it.
Comment 8 Parag 2009-08-21 03:24:00 UTC
(In reply to comment #7)
> Could you please explain me, what is "dead v"? How would you use it as a
> deadkey?
> 
> In /usr/share/X11/locale/*/Compose files I do not see any reference to dead_v,
> it means currently no Compose sequences are using it.
> 

Is this question to me. Then sorry I don't know. I just want to know why dead_V is written in this map and why not to keep it empty? 
Comment 9 Sergey V. Udaltsov 2009-08-21 03:32:40 UTC
Yes, I asked you (sorry, your name is not available in bugzilla).

> Is this question to me. Then sorry I don't know. I just want to know why dead_V
> is written in this map and why not to keep it empty? 
Well, I do not know. Probably Bryce should ask in Launchpad
Comment 10 Parag 2009-08-21 04:12:34 UTC
(In reply to comment #9)
> Yes, I asked you (sorry, your name is not available in bugzilla).
  Sorry. I should have filled that already. 

> 
> > Is this question to me. Then sorry I don't know. I just want to know why dead_V
> > is written in this map and why not to keep it empty? 
> Well, I do not know. Probably Bryce should ask in Launchpad
> 

Ok. lets see what he says.
Comment 11 Bryce Harrington 2009-08-21 10:16:12 UTC
> Ok. lets see what he says.

Beats me.  But you can ask the original reporter via this:

https://edge.launchpad.net/~arky/+contactuser
Comment 12 Parag 2009-09-10 21:44:54 UTC
I will say remove that "dead_V"
Comment 13 sriramchaudhury 2010-07-31 05:44:00 UTC
@parag: The dead_V key is used as a dead key for writing unicode characters ऎ and matra  ॆ  which is generally not used in hindi but in other Indian languages.

So for wx-keymap for hindi we can remove it, but for other Indian language wx-keymap, it is useful.
Comment 14 Ran Benita 2014-02-17 14:35:17 UTC
(In reply to comment #13)
> So for wx-keymap for hindi we can remove it, but for other Indian language
> wx-keymap, it is useful.

There is no "dead_V" keysym, i.e. it doesn't do anything. I think we should remove it, and if you want, add a real keysym instead.
Comment 15 Sergey V. Udaltsov 2014-04-17 23:14:25 UTC
So should anything be fixed, if we do not have any "dead V" currently in the code?
Comment 16 GitLab Migration User 2018-12-28 00:38:14 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/64.

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.