I’m trying to use the indonesian keyboard in keyman (mainly to get around the MAC OSX autocorrect settings while typing Indonesian) but I’m running into a problem in the software. For some reason, when using that keyboard, the keyboard automatically inserts a double quote mark ["] after a period and a space. This results in every new sentence opening with a quotation mark. I’ve dug as far as I can in the UI for the keyboard but can’t find any configuration settings to solve the problem. Can anybody help me?
Which Indonesian keyboard you are having issue with? There are several of them in our keyboard library:
I installed this one.
I just installed Indonesian-Suku and it does NOT put quotes after a period. I suppose I can use that one from now on. It’s just odd that the Indo one adds them and I can’t stop it from happening.
I’m not seeing anything in the code of the keyboard that would cause this. Unless you are on a mobile keyboard then I see one problem in one of the stores, but even so, it’s not giving me the same problem as you had (I’m on Windows). Can you give more details about OS and applications?
The OS details are in the screenshot. I’ve experienced the problem in both MS Word (Mac) and F4Transkript (Mac).
I also just tried installing both keyboards on a Windows machine and i noticed that the Indonesian keyboard automatically inserts a period when hitting space-bar twice, while the Indonesian-Suku keyboard does not.
I hope that helps.
@bennylin Can you look into the issue below with this keyboard of yours: Indonesia Keyboard. The quotation marks got added automatically when a space is pressed twice in a row on macOS, I’ve tested with TextEdit, but as mentioned above it can also happen in MS Office Word. This behavior does not happen in Windows though.
For some reason, when using that keyboard, the keyboard automatically inserts a double quote mark ["] after a period and a space. This results in every new sentence opening with a quotation mark.
It’s possible there is a bug in the Keyman for Mac engine which is causing this. We will be doing some work on the engine later this year and we will check this out at that time.