option to stick to western numerals in foreign input methods[ENHANCEMENT] #60
Comments
itt533
changed the title
|
@fujiwarat just requested to add a direct input mode to ibus-m17n, which is somewhat related to your request. See: #59 But I believe you don't want to press a key to switch to direct input mode each time you want to type western digits and then switch back to “normal” input mode where you would get for example Devanagari letters and Devanagari digits. I believe you want to stay in Devanagari (Or Telugu, Tamil, whatever...) input mode and lock the digits to western digits so you always get Devanagari letters but Western digits without having to press any special key to switch to Western digits. I.e. you want something exactly like the feature I recently implemented in ibus-typing-booster. But why not just use ibus-typing-booster then? It has more features anyway. Is there any particular reason why you want to use ibus-m17n instead of ibus-typing-booster? If you don't need the extra features ibus-typing-booster offers and want just very simple input of an Indian langauge without suggesting word completions, you can switch off almost all of the extras in ibus-typing-booster and make it behave almost exactly like ibus-m17n. This chapter of the documentation shows how to do this: Simulate the behaviour of ibus-m17n: https://mike-fabian.github.io/ibus-typing-booster/docs/user/#2_2_1_1 If you do that, you have something which behaves like ibus-m17n and still has the option in the setup tool to use only western numerals. |
|
By the way, which Indian m17n input methods are you personally using? In ibus/ibus#2530 (comment) you mentioned “hindi”, “telugu”, “itrans”, “inscript telugu”. Which ones exactly are you using? Are you using inscript or inscript2? Or are you using itrans? Or both? And for which languages? |
|
those i'm using are telugu-itrans and sanskrit-itrans. I have been using for long time telugu-inscript and hindi-inscript and i don't think i'll be back to inscript. The way ibus-typing-booster is implemented looks like an improved ibus in ibus. Since ibus interface is heavily buggy i thought it would add as many new problems. Can't you make of ibus-typing-booster an independent program replacing ibus? ibus does not seem to be actively maintained, and there are too many weird problems to report. |
Don't mistake each engine problem and ibus core problelm. |
I don't say it. |
No, that isn’t possible, ibus-typing-booster cannot be an independent program. I think Fujiwara San maintains ibus well and if you really have problems with the core of ibus, open an issue, Fujiwara San will surely help you. As Fujiwara San says, some problems are in the ibus core, some are in the engines, for a normal user this might be confusing and it might not be always obvious for a normal user whether it should be reported agains an ibus engine or against ibus core. |
|
@itt533 I have something for you to test. Please download this file: https://mfabian.fedorapeople.org/misc/te-itrans-itt533.mim Create a Restart ibus: Now when checking which engines ibus knows about, there should be a new one called If using Gnome, open the Gnome control centre and search for that engine and add it. If not using Gnome, use Should look like this in
Switch to that engine and open the setup tool of that ibus-m17n engine. Click on the "Advanced” tab. Should look like this:
By default, the ascii-digits option should be 0. If it is 0, this engine will produce Telugu digits. If you change that option to 1, this engine will produce ASCII digits. You can also use that engine in ibus-typing-booster. After adding it in the ibus-typing-booster setup tool it looks like this:
Select that engine and click on the Hammer and Wrench icon 🛠️. Should look like this:
Here you can choose between 0 and 1 to select whether this input method should produce ascii digits or language specific (i.e. Telugu) digits. I like that system, it requires to apply that change to each of the Indian m17n input methods, but it is a very easy, straigthforward and very safe change. And it makes it possible to select the digit style even in ibus-typing-booster for each input method seperately. The already existing option ☑️ Convert language specific digits to ASCII digits is still useful if you want to switch it globally for all input methods with a single switch. And also if you want to change that option from time to time because changing that option can be bound to a key in the keybindings tab of the ibus-typing-booster setup tool. But having such an option in each engine is also a very good thing I believe. It makes it possible for example to choose that you want ASCII digits in te-itrans but not in hi-itrans for example. |
|
I like that additional option and I think I would like to add that option to all Indian m17n input methods. Very easy, very safe change, also easy to use. |
|
Here I compare the original I like that solution. |
Probably I don't understand it. Fixing it in ibus-m17n is not so hard but safe for me. I think you need to keep the old engine names for the ibus-setup compatibility at least and I also wonder increasing the engine names would even confuse users. And this way might be different between ibus-typing-booster and ibus-m17n. I think asking volunteers can be an idea if the C language enhancements are difficult for @mike-fabian before my resources are used for ibus-m17n. |
|
@mike-fabian i tested your new method te-itrans-itt533.mim. It works well. Anyway i had to restart ibus after setting the 'ascii-digit' option to 1. Since today i have no use at all of telugu digits it's fine. But in the case of sanskrit i use mainly the sanskrit digits and might from time to time need the ascii digits. Therefore i think the best would be to setup a keyboard shortcut like Shift+Super+space to cycle through the available digit scripts. Most of the time it would only be a choice between 2 scripts, i.e. the local one, and ascii one. Super+space is the default shortcut to cycle trough the list of input methods. |
Yes, of course I would not change the engine names. The different engine name te-itrans-itt533 was just for the user @itt533 to test it. If I do that change, I would do it upstream in m17n and the engine names would not change, they would just get an additional option.
Both ibus-typing-booster and ibus-m17n can use these options in the engines in the same way.
Yes, it is one additional way to do it which I think is also helpful. It does not mean that an option to switch the digits for all engines at once like ibus-typing-booster already has is useless, it is just another way to to it which is also useful in its own way. In ibus-typing-booster this gives more fine grained control, instead of using the global option for all engines, a user could choose to use ASCII digits for te-itrans but not for hi-itrans for example. |
In ibus-typing-booster you can do that. Shortly after I had implemented the new option ☑️ Convert language specific digits to ASCII digits in ibus-typing-booster, I also added the command
By default it is not bound to any key. But you can bind this to any key you like to have a keyboard shortcut to switch between the language specific (Telugu, Sanskrit, ...) and the ASCII digits. |
|
@itt533 You could also use ibus-m17n for te-itrans and ibus-typing-booster with the key-binding to toggle the ASCII digits for Sanskrit if you like. |
|
I wanted to disable the small box that suggests words that it memorised, I checked "off the record", and deleted its dictionary and now it's fine. Isn't there any other way for that? Is there a way so that all input is done in real-time so that i don't need to hit |
This chapter in the documentation: Simulate the behaviour of ibus-m17n https://mike-fabian.github.io/ibus-typing-booster/docs/user/#2_2_1_1 describes the settings to use if one wants ibus-typing-booster to behave very close to ibus-m17n. That is similar to what you did. The small remaining difference to ibus-m17n is that a word is committed only after a |
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
when selecting an indic input method like 'hindi', 'telugu', one automatically
gets numerals too in those languages. Most of these people have adopted
the western numerals, therefore there should be an option allowing or
disabling the chosen language numerals. That is how it is in latex, and libreoffice
Describe the solution you'd like
A clear and concise description of what you want to happen.
There should be an option locking numerals to western only
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
ibus-typing booster recently implement this feature
The text was updated successfully, but these errors were encountered: